Thank you for the reply. That gets me to the same workaround I had before
though. The problem is that it still shows that the playbook failed
overall as the host is shown in red at the end because the unreachable
error does not trigger the rescue block, and it still gets shown at the end
as
You can do this now w/o waiting for a new feature.
- block:
- win_ping:
ignore_unreachable: true
register: ping
- name: this forces a recoverable fail
assert:
that:
- not ping['unreachable']|default(False)
- # depending on connection plugin, you can inspect ping['msg']
For some background, this was initially an RFE that was opened from a Red
Hat support ticket. https://github.com/ansible/ansible/issues/76227.
Here's where I'm struggling with this. I have a playbook that creates a VM
in vCenter, sets it up for WinRM, and then applies some OS configs (updates
