Potential client issue
-
This is aimed more at Joe, but I’ll tag the @Senior-Developers on this one.
I think there could now be a potential scenario where computers will never turn off.
I (and co-workers) plan on using the new power management feature to shutdown computers at 10 pm, mon-fri.
From what I’ve observed, when a client update happens on a host, the service shuts down, and then all is well after the next reboot.
What this could cause in an environment where the only shutdown command is coming from the client, but the client is not active due to an upgrade, computers could potentially be left on for a very, very long time before being noticed.
Just wanted to bring this up.
My idea of a fix would be an option to optionally have computers reboot during the update process, and allow this reboot to be aborted by the user if they so desire.
-
@Wayne-Workman if the client doesn’t auto start with the update, then that is a bug. As for restarting during auto updating? Please no. The auto update process is already complex as is. It’s amazing that it even works on every OS.
-
@Joe-Schmitt Ok then we have a bug. It’s not been restarting for me here recently.
-
Please post a fog.log from a client that didn’t auto start when updating.
-
@Joe-Schmitt I’ll do that Monday.
