-
Notifications
You must be signed in to change notification settings - Fork 177
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
win_update: WinRM failed to connect post reboot #143
Comments
The playbook is working well and total time takes to reach the above stage is:
Seems like the main issue is here:
And this command is exiting with just few tries. Because the system reboot is complete and its just checking all the policies. So that also has to be considered. Because as per my observation, after this failure, with in 30-40 secs system is back to login screen. |
Hello there! I believe I'm experiencing some kind of similar problem using win_updates module, trying to install updates on a fresh Windows 2016 server... My feeling is that the module could have an issue managing multiple reboots required by the updates installation. This is the log I'm getting (obfuscating sensitive data):
What I understand:
The precise error raised on this step is:
Monitoring aside the server itself, I can see it rebooting multiple times during the update process. Could it be possible the module believes the server is up and running fine, but a reboot takes place just after that (caused by an update just installed)? I don't see any easy fix for that, any help welcome! Thanks a lot! |
Agree with you. Fix is not easy but a fix has to be applied. Currently win_update module is not atall able to handle the system updates due to multiple reboot. May be some system validation logic has to be implemented in it. |
SUMMARY
win_update module is not responding properly to reboot_timeout and throwing the traceback even if the update & system reboot is successful.
ISSUE TYPE
COMPONENT NAME
ANSIBLE VERSION
OS / ENVIRONMENT
STEPS TO REPRODUCE
EXPECTED RESULTS
Should complete the update successfully
ACTUAL RESULTS
Failed with the following traceback:
The text was updated successfully, but these errors were encountered: