20:00:00 <nitzmahone> #startmeeting Ansible Windows Working Group
20:00:00 <zodbot> Meeting started Tue May  4 20:00:00 2021 UTC.
20:00:00 <zodbot> This meeting is logged and archived in a public location.
20:00:00 <zodbot> The chair is nitzmahone. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:00:00 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
20:00:00 <zodbot> The meeting name has been set to 'ansible_windows_working_group'
20:00:03 <nitzmahone> yeah
20:00:06 <nitzmahone> #chair jborean93
20:00:06 <zodbot> Current chairs: jborean93 nitzmahone
20:00:10 <jborean93> hey
20:00:46 <nitzmahone> #info agenda: https://github.com/ansible/community/issues/581
20:00:55 <nitzmahone> Nothing new, so
20:00:57 <nitzmahone> #topic open floor
20:01:21 <jborean93> only thing to add is that I'm planning on merging win_reboot sometime soon https://github.com/ansible-collections/ansible.windows/pull/214
20:01:24 <nitzmahone> Woot
20:01:25 <jborean93> just 1 more test I want to run
20:02:10 <nitzmahone> Hopefully that'll fix the post-update reboot fun for most folks
20:02:40 <briantist> oh hi
20:02:44 <jborean93> it still doesn't fully  solve the reboot after applying updates on a reboot but that's really rare today and you could get lucky and it just works
20:03:27 <jborean93> if you are unlucky the test_command check happens at that sweet spot when the key is present but just before the host goes back down again. I think it happened to me 1 time out of the 50 times I ran that scenario locally
20:05:26 <jborean93> but that's an existing problem today and I ran out of juice trying to find a way around that
20:05:51 <briantist> what if we just run it twice 😛
20:06:02 <nitzmahone> SILENT INTERNAL RETRIES FOR ALL!
20:06:08 <briantist> lollll
20:06:22 <jborean93> I tried detecting if a shutdown was in progress after the test_command but alas that didn't work
20:06:54 <jborean93> also that check was icky as you need to call shutdown yourself and check if it had an rc of 1190 and cancel it if it did not
20:07:03 <nitzmahone> Always possible to have a race for those anyway... If Microsoft can't be bothered to make their flagship remote management resilient to such problems, I'm not sure how much we can paper over it
20:07:11 <jborean93> yea
20:07:29 <jborean93> considering I've only ever encountered the double reboot on an update on 2008 R2 I decided it just wasn't worth my time
20:07:29 <nitzmahone> (and every time we've pointed this problem out, it's always kinda "shrug")
20:08:03 <briantist> yeah, it was an honorable to goal to try to work around the issue of updates initiating restarts but ultimately it's out of scope for this, win_reboot does what it's supposed to
20:08:05 <jborean93> or why do you want to do that?
20:08:42 <briantist> "have you considered not needing the machine to be up consistently?"
20:10:34 <nitzmahone> Meh, Powershell is just for remote shells anyway, nobody uses it for automation /s
20:12:44 <briantist> "Shoulda used PowerShell  Workflows" 🤦‍♂️
20:12:49 <jborean93> lol
20:14:50 <jborean93> apart from that I don't have anything special to add
20:14:58 <briantist> same
20:15:10 <nitzmahone> OK cool- til next week then... Thanks all!
20:15:12 <nitzmahone> #endmeeting