]> git-server-git.apps.pok.os.sepia.ceph.com Git - ceph.git/commit
qa: barbican: restrict python packages with upper-constraints 59326/head
authorTobias Urdin <tobias.urdin@binero.com>
Thu, 15 Aug 2024 15:17:14 +0000 (17:17 +0200)
committerCasey Bodley <cbodley@redhat.com>
Mon, 19 Aug 2024 17:23:35 +0000 (13:23 -0400)
commitbdfaf1f995bc8c842576320decd276bb869078fc
tree9e547d1794e0b1136fb77ee89542aa4a9129d10b
parent56fd5b351507f92fd1531bbfb42df967f9fbe713
qa: barbican: restrict python packages with upper-constraints

We install barbican by doing a pip install directly on the
cloned git repository but we don't honor the upper-constraints
from the OpenStack Requirements project that handles what
versions is supported.

This changes the pip install command that we issue when
installing barbican to honor the requirements for the
version (derived from the branch) that we use, in
this case it's the 2023.1 release upper-constraints [1].

This prevents us from pulling in untested Python packages.

This only updates Barbican because for the Keystone job
we dont directly issue pip but install using tox using the
`venv` environment which already by default sets the
constraints as you can see in [2].

[1] https://releases.openstack.org/constraints/upper/2023.1
[2] https://github.com/openstack/keystone/blob/stable/2023.1/tox.ini#L12

Fixes: https://tracker.ceph.com/issues/67444
Signed-off-by: Tobias Urdin <tobias.urdin@binero.com>
(cherry picked from commit bbcb820c779ed6c48ff4fa7c10730228f43e9305)
qa/tasks/barbican.py