As part of the STX-Openstack upversion to Epoxy, some of the python packages are being upversioned to latest version supported on Epoxy [1]: python-aodhclient 3.5.1-3 -> 3.7.1-2 Commit: 95d7c59e3994d4ac4430d301ba57a6639dbd4b16 (tag: debian/3.7.1-2) python-barbicanclient 5.7.0 -> 7.1.0-3 Commit: 1b0b04f946fdb6d7259eb1b41258b3eea214ddfc (tag: debian/7.1.0-3) python-glanceclient 4.5.0 -> 4.8.0-2 Commit: 1d0db5390f79f514f82bed7f8d0212d3b1e3a5cb (tag: debian/4.8.0-2) python-heatclient 3.5.0 -> 4.1.0-3 Commit: da2f174d6be6413152f5ee007a9209fcadcdd167 (tag: debian/4.1.0-3) python-ironicclient 5.5.0 -> 5.10.0-4 Commit: 37456fd0d53bb2a4ff45eaf2ea3ca262f23ffc3c (tag: debian/5.10.0-4) python-keystoneclient 5.4.0-2 -> 5.6.0-2 Commit: 039365a62afb14f10b6ed82c30b4bbb230431e34 (tag: debian/5.6.0-2) python-neutronclient 11.2.0 -> 11.4.0-2 Commit: 081367e8d1fbd6dc5155ba7fc279f0ef841565c3 (tag: debian/11.4.0-2) openstacksdk 3.0.0-3 -> 4.4.0-5 Commit: be61953fe093f00888b543956f78e63e89e38724 (tag: debian/4.4.0-5) Important note: the openstacksdk patch [2] that was removed in this update was because the code was already added [3] in the new openstacksdk version. Test Plan: - PASS: Build all STX-O packages and wheels - PASS: Build STX-O tarball - PASS: Build STX docker images - PASS: Assert clients version on upgraded built images - BLOCKED: Apply STX-O overriding generated images The apply failed due to an issue related to db_sync, which will be handled in the Task: 53501 [1] https://releases.openstack.org/epoxy/index.html [2] https://opendev.org/starlingx/openstack-armada-app/src/branch/master/upstream/openstack/python-openstacksdk/debian/patches/0001-Fix-volume-backup-restore-response.patch [3] https://review.opendev.org/c/openstack/openstacksdk/+/931755 Depends-on: https://review.opendev.org/c/starlingx/tools/+/969154 Story: 2011516 Task: 52973 Change-Id: I1b7ecf85529b05f6cac1927a86306e2bc8847178 Signed-off-by: jbarboza <joaopedro.barbozalioneza@windriver.com>
This repo is for https://opendev.org/openstack/python-barbicanclient
Changes to this repo are needed for StarlingX and those changes are not yet merged. Rather than clone and diverge the repo, the repo is extracted at a particular git SHA, and patches are applied on top.
As those patches are merged, the SHA can be updated and the local patches removed.