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
ansible-lint fails after upgrade to 4.1.1 #562
Comments
|
I don't know what that means but I'll investigate. Thanks. |
4.1.0 also will not install on a clean RHEL7 VM.
|
Same problem, same solution + anyway it's failing to install ruamel, not ansible-lint. |
I mean same as #565 (comment) |
I know but it's a dependency which never failed with 4.0. I suspect it's a new one, is it? Either way, it breaks ansible-lint. |
|
So the issue is that As a workaround use pip install --user --only-binary ruamel.yaml ansible-lint or pip install --user --prefer-binary ansible-lint Ultimate/universal solution that prevents similar future problems:Use a separate virtualenv for ansible-lint and use pip-tools to generate a constraints file with exact versions of all indirect dependencies with dist hashes. |
OK, thanks, that's good to know. |
The .whl for 0.16.1 just got uploaded |
test.yml
steps to reproduce the issue:
error:
it solved the issue for me: |
Seems to be working now on a clean isntallation using 4.1.0 and 4.1.1a2. Thanks. |
Issue Type
After upgrading to 4.1.1 I get this error on every run. I tried 4.1.1.a0, and reverting back through 4.1.0 to 4.0.1. No change. I also noted that the upgrade pused ansible to 2.8.3, from my previously installed 2.8.2 so I reverted that as well. Nothing has helped. I suspect something in the dependencies might have broken it but I don't know what they were. My builds are now broken due to failing lint checks and I am so far unable to fix this.
Ansible and Ansible Lint details
Desired Behaviour
No error.
Actual Behaviour (Bug report only)
The text was updated successfully, but these errors were encountered: