-
Notifications
You must be signed in to change notification settings - Fork 23.9k
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_updates can't update reboot_required status on WinServer 2019 #59056
Comments
Files identified in the description: If these files are inaccurate, please update the |
Files identified in the description: If these files are inaccurate, please update the |
This could be a problem with the specific update - it has a lot of ui components, it might require an interactive logon to complete correctly |
@pawellrus - has this happened with any other update since? |
@ShachafGoldstein, i will check it soon. May be on next week. |
I've seen this too, and most recently today trying to install the round of September 2019 updates. It seems related to the 2019-09 cumulative rollup.. this keeps repeating over and over: 'WINRM STDOUT {"updates":{"644bb2c6-0f42-4216-8c9a-96541b6fbaa3":{"id":"644bb2c6-0f42-4216-8c9a-96541b6fbaa3","title":"2019-09 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB4512578)","categories":["Security Updates"],"kb":["4512578"],"installed":true}},"failed_update_count":0,"found_update_count":1,"changed":false,"reboot_required":true,"installed_update_count":1,"filtered_updates":{}}^[[0m' |
Hello again. September updates was installed without this issue in my environment. |
update: I seem to be able to work around the issue by forcing a reboot before calling the win_updates module... |
Got the same infinite reboot cycle today again. |
Can you say which updates were installed? since that error is a very generic error of WU it has hard to pinpoint the issue. |
That was October cumulative update KB4519338. I has another issue recently with searching of new updates. New updates weren't been found when running process from ansible. But starting update process from GUI gave a couple of new updates. But that issue gone after some time. I didn't experienced such problems at older versions of WinServer. There is definetely some issue in server 2019 that makes win_update module unreliable. |
I Don't we have any way to resolve this. it seems like changes in how MS
deploys updates to these versions. they require human intervention.
…On Mon, 18 Nov 2019 at 09:27, pawellrus ***@***.***> wrote:
That was October cumulative update KB4519338.
I has another issue recently with searching of new updates. New updates
weren't been found when running process from ansible. But starting update
process from GUI gave a couple of new updates. But that issue gone after
some time.
I didn't experienced such problems at older versions of WinServer. There
is definetely some issue in server 2019 that makes win_update module
unreliable.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#59056?email_source=notifications&email_token=ACV27RV6OVKBI2LVQ5IX6JTQUI7VBA5CNFSM4IC5CDX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEJOM4Y#issuecomment-554886771>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACV27RXW2RD3JPQYOVS2NLLQUI7VBANCNFSM4IC5CDXQ>
.
|
Same issue is happening for the November cumulative update (KB4523205). |
Adding a win_reboot just before the start of win_update seems to have provided a valid work around. BTW, In my scenario this playbook is being ran on a new system build. |
Do you see the server rebooting in your scenarios?, could the issue be around not actually rebooting the server? |
Yes, it's kicking off a reboot shortly after the attempted install. It's as if it gets a completed return call rather than a wait. Adding the manual reboot before the win_update process is working on multiple runs now. |
So if you simply reboot and then install updates everything works? Or you reboot between updates? Can you post a verbose output of a failed one and a working one? |
@mhazri Seems you are talking about something else, this issue is about reboot loop caused by Ansible. |
Issue has been migrated to ansible-collections/ansible.windows#25 |
SUMMARY
I faced with a strange issue when I was trying to install updates for Windows Server 2019.
Playbook stuck in rebooting loop.
ISSUE TYPE
COMPONENT NAME
ANSIBLE VERSION
STEPS TO REPRODUCE
EXPECTED RESULTS
Windows Server gets updated.
ACTUAL RESULTS
reboot_required status isn't get lifted after ansible initiated reboot. Playbook stuck in reboot loop.
User needs to log on to server and reboot server from Windows Update GUI.
The text was updated successfully, but these errors were encountered: