win_reboot: Default reboot_timeout (600 sec) may not suffice #47229
Labels
affects_2.8
This issue/PR affects Ansible v2.8
bug
This issue/PR relates to a bug.
module
This issue/PR relates to a module.
support:core
This issue/PR relates to code supported by the Ansible Engineering Team.
windows
Windows community
SUMMARY
Currently the win_reboot module comes with a pre-configured default value of 600 seconds for the reboot_timeout. For normal reboot this may suffice, but a few conditions could result in unexpected failures.
The system may have updates applied before rebooting, which results in additional pre-boot and post-boot processing, and occasionally additional reboots.
The system may have been configured with a delayed startup of the WinRM service, a necessary mitigation for issues related to WinRM being available before the system was fully settled (causing unexpected behavior, e.g. AD operations failing).
Physical systems may take a longer time to shut down and reboot.
Currently there is no straight-forward way for Ansible to check if updates have been applied and take these into account when rebooting. So it is probably best for the user to increase the reboot_timeout to something higher than the highest value you may encounter, like
reboot_timeout: 3600
.This ticket exists to discuss possible workarounds or improvements to the general issue.
ISSUE TYPE
COMPONENT NAME
win_reboot
ANSIBLE VERSION
Possibly every version
The text was updated successfully, but these errors were encountered: