You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be better to determine if the program is running on a hypervisor host vs. a guest machine and configure the reboot time differently. For example, I can imagine configuring the reboot time to 5 o'clock for hypervisor hosts instead.
The text was updated successfully, but these errors were encountered:
Wouldn't it be better to reboot the hypervisor first. Then possible mandatory reboots from vm's are already done. Sure there are some Machines that only get paused while the hypervisor reboots but on some hypervisors they get restarted.
Currently, the reboot time is configured to be 4 o'clock in the morning for all hosts.
autopilot/debian-enable-unattended-upgrades.sh
Lines 15 to 16 in 9a80360
autopilot/debian-enable-unattended-upgrades.sh
Lines 177 to 178 in 9a80360
It would be better to determine if the program is running on a hypervisor host vs. a guest machine and configure the reboot time differently. For example, I can imagine configuring the reboot time to 5 o'clock for hypervisor hosts instead.
The text was updated successfully, but these errors were encountered: