Check for successful ansible --version call
#2949
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ssbarnea
requested changes
Nov 4, 2020
Check that the `ansible --version` command executes successfully or raise a subprocess.CalledProcessError. Otherwise, Ansible might print a message starting with "the full traceback was:" to stdout, eventually leading to the following cryptic exception: packaging.version.InvalidVersion: Invalid version 'full' Signed-off-by: Janne Pulkkinen <janne.pulkkinen@protonmail.com>
Matoking
force-pushed
the
ansible_version_check
branch
from
553017b
to
b387a3c
Compare
ssbarnea
approved these changes
Nov 4, 2020
|
Obsoleted byt #2956 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Check that the
ansible --versioncommand executes successfully or raise a subprocess.CalledProcessError. Otherwise , Ansible might print a message starting with "the full traceback was:" to stdout, eventually leading to the following cryptic exception:With the check in place, the following exception is printed instead:
PR Type