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

Do not restart after updates #127

Open
zenmaster24 opened this issue Apr 13, 2023 · 3 comments
Open

Do not restart after updates #127

zenmaster24 opened this issue Apr 13, 2023 · 3 comments

Comments

@zenmaster24
Copy link

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

@rgl
Copy link
Owner

rgl commented Apr 13, 2023

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)?

@zenmaster24
Copy link
Author

zenmaster24 commented Apr 13, 2023

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?

@rgl
Copy link
Owner

rgl commented Apr 13, 2023

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.

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

No branches or pull requests

2 participants