-
Notifications
You must be signed in to change notification settings - Fork 43
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
urllib3 / six install broken in ansible-ee-tests-stable-2.12 / ansible-ee-tests-stable-devel environments #1497
Comments
the python38-six inclusion is going to change to python39-six very soon, we also need to do a review of the amazon.aws bindep.txt inclusions so that might be a better long term solution? I'll try to put up a test PR later today to explore that idea. |
From what I could follow, the inclusion of The next thing I was going to try was actually updating ansible.netcommon to replace the bindep with a requirements.txt dep. |
…-stable-2.12 non voting for amazon.aws (#1498) Make ansible-ee-tests-latest globally non-voting and ansible-ee-tests-stable-2.12 non voting for amazon.aws ansible-latest (ie devel) is expected to break from time to time, with things like new sanity tests landing. Such changes will likely result in new ignore file entries being needed until cleanup can be applied. While we should be reacting reasonably quickly to this, we shouldn't instantly break CI for multiple collections. ansible-ee-tests-stable-2.12 and ansible-ee-tests-latest are currently broken for amazon.aws due to #1497 this is a problem with the containers, the unit and sanity tests are running fine in the 'standard' environments.
…-stable-2.12 non voting for amazon.aws (ansible#1498) Make ansible-ee-tests-latest globally non-voting and ansible-ee-tests-stable-2.12 non voting for amazon.aws ansible-latest (ie devel) is expected to break from time to time, with things like new sanity tests landing. Such changes will likely result in new ignore file entries being needed until cleanup can be applied. While we should be reacting reasonably quickly to this, we shouldn't instantly break CI for multiple collections. ansible-ee-tests-stable-2.12 and ansible-ee-tests-latest are currently broken for amazon.aws due to ansible#1497 this is a problem with the containers, the unit and sanity tests are running fine in the 'standard' environments.
Tests using boto3/botocore are failing due to a broken urllib/six install. This is likely caused by ansible.netcommon installing python38-six, which then gets reinstalled via pip
See also:
urllib3/urllib3#1518
Example failure:
https://ansible.softwarefactory-project.io/zuul/build/87e61df77f2d42688bb020c478d26f58/logs ( https://24c75d1ca6f3a9bcbe40-22bfaf5d5c3577156f2cc8ae23baf11e.ssl.cf5.rackcdn.com/775/f794724027764404876902afbe7de98506334590/check/ansible-ee-tests-stable-2.12/87e61df/job-output.txt )
The text was updated successfully, but these errors were encountered: