openstack-tox: ERROR: Cannot install cryptography<37.0.0

Bug #1996917 reported by Amol Kahat
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Triaged
Critical
Unassigned

Bug Description

openstack-tox-py* jobs are failing

Actual Error
```
2022-11-17 12:25:46.284128 | ubuntu-focal | ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 7.1/7.1 MB 66.1 MB/s eta 0:00:00
2022-11-17 12:25:47.691958 | ubuntu-focal | Preparing metadata (setup.py): started
2022-11-17 12:25:48.568156 | ubuntu-focal | Preparing metadata (setup.py): finished with status 'done'
2022-11-17 12:25:48.979137 | ubuntu-focal | ERROR: Cannot install cryptography<37.0.0 because these package versions have conflicting dependencies.
2022-11-17 12:25:48.979641 | ubuntu-focal |
2022-11-17 12:25:48.979661 | ubuntu-focal | The conflict is caused by:
2022-11-17 12:25:48.979667 | ubuntu-focal | The user requested cryptography<37.0.0
2022-11-17 12:25:48.979671 | ubuntu-focal | The user requested (constraint) cryptography===38.0.2
2022-11-17 12:25:48.979699 | ubuntu-focal |
2022-11-17 12:25:48.979717 | ubuntu-focal | To fix this you could try to:
2022-11-17 12:25:48.979722 | ubuntu-focal | 1. loosen the range of package versions you've specified
2022-11-17 12:25:48.979727 | ubuntu-focal | 2. remove package versions to allow pip attempt to solve the dependency conflict
2022-11-17 12:25:48.979731 | ubuntu-focal |
2022-11-17 12:25:48.979898 | ubuntu-focal | ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
2022-11-17 12:25:49.217249 | ubuntu-focal | ERROR: invocation failed (exit code 1)
2022-11-17 12:25:49.217720 | ubuntu-focal | ERROR: could not install deps [-c/home/zuul/src/opendev.org/openstack/requirements/upper-constraints.txt, -r/home/zuul/src/opendev.org/openstack/tripleo-ansible/requirements.txt, -r/home/zuul/src/opendev.org/openstack/tripleo-ansible/test-requirements.txt, -r/home/zuul/src/opendev.org/openstack/tripleo-ansible/ansible-requirements.txt]; v = InvocationError('/home/zuul/src/opendev.org/openstack/tripleo-ansible/.tox/py38/bin/python -m pip install -c/home/zuul/src/opendev.org/openstack/requirements/upper-constraints.txt -r/home/zuul/src/opendev.org/openstack/tripleo-ansible/requirements.txt -r/home/zuul/src/opendev.org/openstack/tripleo-ansible/test-requirements.txt -r/home/zuul/src/opendev.org/openstack/tripleo-ansible/ansible-requirements.txt', 1)
2022-11-17 12:25:49.217760 | ubuntu-focal | py38 finish: getenv /home/zuul/src/opendev.org/openstack/tripleo-ansible/.tox/py38 after 6.50 seconds
2022-11-17 12:25:49.218184 | ubuntu-focal | ___________________________________ summary ____________________________________
2022-11-17 12:25:49.218219 | ubuntu-focal | ERROR: py38: could not install deps [-c/home/zuul/src/opendev.org/openstack/requirements/upper-constraints.txt, -r/home/zuul/src/opendev.org/openstack/tripleo-ansible/requirements.txt, -r/home/zuul/src/opendev.org/openstack/tripleo-ansible/test-requirements.txt, -r/home/zuul/src/opendev.org/openstack/tripleo-ansible/ansible-requirements.txt]; v = InvocationError('/home/zuul/src/opendev.org/openstack/tripleo-ansible/.tox/py38/bin/python -m pip install -c/home/zuul/src/opendev.org/openstack/requirements/upper-constraints.txt -r/home/zuul/src/opendev.org/openstack/tripleo-ansible/requirements.txt -r/home/zuul/src/opendev.org/openstack/tripleo-ansible/test-requirements.txt -r/home/zuul/src/opendev.org/openstack/tripleo-ansible/ansible-requirements.txt', 1)
2022-11-17 12:25:49.302015 | ubuntu-focal | ERROR
```

Logs:
- https://f6314bbe689272b182bf-704d2e5cde896695f5c12544f01f1d12.ssl.cf1.rackcdn.com/863876/2/gate/openstack-tox-py38/36304a8/job-output.txt
- https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_912/863876/2/gate/openstack-tox-py39/912bb29/job-output.txt

Tags: ci
Revision history for this message
Amol Kahat (amolkahat) wrote :

This might be caused because of pinning cryptography requirements in ansible-requirements[1].

[1] https://opendev.org/openstack/tripleo-ansible/commit/c0bc395ab494ee18e77fba608cdd40762c7b8c51

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to tripleo-ansible (master)

Related fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/tripleo-ansible/+/864917

Revision history for this message
Rabi Mishra (rabi) wrote :

I mentioned this on irc but was probably not clear. https://review.opendev.org/c/openstack/tripleo-ansible/+/863876 adding uc[1] to tox* jobs and that's why it's failing with the pin. This won't impact other tripleo-ansible patches. Cedric is working on removing the pin though so that can use uc for those tox targets.

Note: That patch passed the check before we added the pin hence confusing.

[1] https://review.opendev.org/c/openstack/tripleo-ansible/+/863876/2/tox.ini

Revision history for this message
Amol Kahat (amolkahat) wrote :

Thanks Rabi. I'll abandon my patch.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on tripleo-ansible (master)

Change abandoned by "amolkahat <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/tripleo-ansible/+/864917
Reason: In favor of https://review.opendev.org/c/openstack/tripleo-ansible/+/863876/

Revision history for this message
Ronelle Landy (rlandy) wrote :

Watching these three patches:

<opendevreview> Cedric Jeanneret proposed openstack/tripleo-ansible master: Trigger all molecule jobs if we modify molecule-requirements https://review.opendev.org/c/openstack/tripleo-ansible/+/864994
<opendevreview> Cedric Jeanneret proposed openstack/tripleo-ansible master: Remove cryptography pin https://review.opendev.org/c/openstack/tripleo-ansible/+/864906
<opendevreview> Cedric Jeanneret proposed openstack/tripleo-ansible master: Mass corrections of molecule scenarios https://review.opendev.org/c/openstack/tripleo-ansible/+/864999

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.