Backport: Raise AnsibleConnectionError on winrm connnection errors #52226
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
Currently all uncaught exceptions of the requests library that is used in winrm will lead to an "Unexpected failure during module execution".
Instead of letting all exceptions bubble up we catch the connection related errors (inkl. timeouts) and re-raise them as
AnsibleConnectionError
so Ansible will mark the host as unreachable and exit with the correct return code.This is especially important for Zuul (https://zuul-ci.org) to distinguish between failures and connection/host related errors.
Backport of #51744.
ISSUE TYPE
COMPONENT NAME
winrm
ADDITIONAL INFORMATION