when reboot required, unit status should be something else than "active"
Bug #1907205 reported by
Nobuto Murata
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| charm-sysconfig |
Fix Released
|
Wishlist
|
Unassigned | ||
Bug Description
When the charm is deployed and the unit requires a reboot, then unit status as blocked or something would make sense than just being "active".
sysconfig/0* active idle 10.X.X.Z reboot required. Changes in: /etc/systemd/
Revision history for this message
| Giuseppe Petralia (peppepetra) wrote | #1 |
| Changed in charm-sysconfig: | |
| importance: | Undecided → Wishlist |
| tags: | added: bseng-221 |
Revision history for this message
| Chi Wai CHAN (raychan96) wrote | #2 |
| Changed in charm-sysconfig: | |
| status: | New → Fix Released |
To post a comment you must log in.
Can we also add an nrpe check that goes at least into Warning if a reboot is needed?
This will help the operator noticing it.