Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unattended upgrades: Configure different reboot time for hypervisors vs. guests #4

Open
amotl opened this issue Mar 27, 2022 · 1 comment · May be fixed by #6
Open

Unattended upgrades: Configure different reboot time for hypervisors vs. guests #4

amotl opened this issue Mar 27, 2022 · 1 comment · May be fixed by #6

Comments

@amotl
Copy link
Member

amotl commented Mar 27, 2022

Currently, the reboot time is configured to be 4 o'clock in the morning for all hosts.

# # Configure reboot time. Default is `04:00`.
# export UNATTENDED_REBOOT_TIME=22:00

# If automatic reboot is enabled and needed, reboot at the specific time.
Unattended-Upgrade::Automatic-Reboot-Time "${UNATTENDED_REBOOT_TIME:-04:00}";

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.

@Tonkenfo
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants