-
Notifications
You must be signed in to change notification settings - Fork 71
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
Do not restart after updates #127
Comments
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)? |
I did - didnt work.
You can use the flag |
Oh that's a bummer :-(
Not sure what you mean be |
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
The text was updated successfully, but these errors were encountered: