Open zenmaster24 opened 1 year ago
No. Handling restarts is a typical requirement for applying windows updates. It has to be handled by this provisioner because packer does not have loops.
Did you try the restart_timeout parameter on this provisioner)?
Did you try the restart_timeout parameter on this provisioner)?
I did - didnt work.
It has to be handled by this provisioner because packer does not have loops.
You can use the flag IgnoreReboot
with Install-WindowsUpdate - are you saying this provisioner will persist across reboots requested by an update that has been installed?
Did you try the restart_timeout parameter on this provisioner)?
I did - didnt work.
Oh that's a bummer :-(
It has to be handled by this provisioner because packer does not have loops.
You can use the flag
IgnoreReboot
with Install-WindowsUpdate - are you saying this provisioner will persist across reboots requested by an update that has been installed?
Not sure what you mean be persist
, but, this provider will loop installing updates and rebooting until the updates are installed.
Hi,
Having an issue where the recent windows update KB5025230 is causing the instance to take a long time to reboot - Packer errors with the message
retry count exhausted. Last err: http response error: 401 - invalid content type
.Is it possible to set the windows-update provisioner to not reboot after the updates are applied, and instead handle a restart with the windows-restart provisioner which has a restart_timeout parameter?
Thanks