-
Notifications
You must be signed in to change notification settings - Fork 675
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
Since 6.16 ANSIBLE_VERBOSITY=4 causes an unhandeld exception #3522
Closed
Labels
Comments
asmacdo
added a commit
to asmacdo/molecule
that referenced
this issue
Jun 5, 2023
ansible-compat 4.0.1 included a breaking change. If we want to use latest, minimum version must be at least 4.0.1. ansible-compat < 4.1.2 has an issue that causes an unhandled exception for certain log levels. ansible/ansible-lint#3522 Since this issue caused CI trouble, we go ahead and bump to 4.1.2.
zhan9san
pushed a commit
to ansible/molecule
that referenced
this issue
Jun 7, 2023
* Use run, not exec, for ansible-compat 4.0.2 4.0.2 dropped the use of `exec`, needs to be replaced with `run` Fixes #3903 ansible/ansible-compat#256 * bump ansible-compat 4.1.2 ansible-compat 4.0.1 included a breaking change. If we want to use latest, minimum version must be at least 4.0.1. ansible-compat < 4.1.2 has an issue that causes an unhandled exception for certain log levels. ansible/ansible-lint#3522 Since this issue caused CI trouble, we go ahead and bump to 4.1.2. * fixup * [DATALAD RUNCMD] recompile requirements.lock.txt === Do not change lines below === { "chain": [], "cmd": "pip-compile --no-annotate --output-file=.config/requirements-lock.txt --resolver=backtracking --strip-extras --unsafe-package=ruamel-yaml-clib pyproject.toml", "exit": 0, "extra_inputs": [], "inputs": [], "outputs": [], "pwd": "." } ^^^ Do not change lines above ^^^ * fix tests for command init role and init scenario Currently the tests fail for `test_command_init_role` and `test_command_init_scneario`. The tests execute `ansible-lint` on the newly-created roles and the linter recently got more restrictive, so we now have to adapt. * [DATALAD RUNCMD] recompile requirements.txt === Do not change lines below === { "chain": [], "cmd": "pip-compile --extra=docs --extra=test --no-annotate --output-file=.config/requirements.txt --resolver=backtracking --strip-extras pyproject.toml", "exit": 0, "extra_inputs": [], "inputs": [], "outputs": [], "pwd": "." } ^^^ Do not change lines above ^^^ * Fake 3.9 for autogenerated files I used 3.10, but CI will run this on 3.9, and fail if there is a diff. This means it is safe to change this by hand, since it will be checked. --------- Co-authored-by: Daniel Ziegenberg <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
When setting ANSIBLE_VERBOSITY=4, parsing the json output of ansible-galaxy fails as STDOUT contains debug information prior to the json string.
Affected line: https://github.com/ansible/ansible-compat/blob/main/src/ansible_compat/runtime.py#L245
Issue Type
OS / ENVIRONMENT
STEPS TO REPRODUCE
Put an arbitrary playbook into a folder and run the commands below.
The text was updated successfully, but these errors were encountered: