Reboot activity should only be considered complete after the reboot, not at delivery time
Bug #792360 reported by
Andreas Hasenack
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Landscape Client |
Invalid
|
Wishlist
|
Unassigned | ||
Bug Description
Currently, the reboot activity is deemed complete as soon as it was delivered to the client and the client reported back saying it acted on it.
We do use a 5min grace period on the client, though, so the reboot will really only happen 5min after the delivery.
We should either get rid of this grace period, or change the way the client reports back the success so that this reporting only happens after the reboot. In other words, when (and if) the machine comes back probably.
Otherwise, what happens is that the administrator thinks the reboot was done already when the activity is shown as succeeded, and might be surprised when he does something else to the machine soon thereafter and finds out it suddenly reboots.
| summary: |
- Reboot acivity should only be considered complete after the reboot, not + Reboot activity should only be considered complete after the reboot, not at delivery time |
Revision history for this message
| 🤖 Landscape Builder (landscape-builder) wrote | #1 |
| Changed in landscape-client: | |
| status: | New → Invalid |
To post a comment you must log in.
This bug has not seen any activity in the last 6 months, so it is being automatically closed.
If you are still experiencing this issue, please feel free to re-open.
Landscape Team