-
Notifications
You must be signed in to change notification settings - Fork 906
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[stable-only] Cap bandit to v1.6.2 and fix constraints
This patch has multiple fixes to unblock gate. 1. bandit We don't have bandit requirements in upper-constraints, so we need to cap it in stable branches manually to work with Python 2.7, as bandit 1.6.3 [1] release has dropped support for py2 [2] but the release is faulty and pip still picks it up for py2 [3][4]. 2. pip resolver With the new pip resolver the following issues needed to be fixed: * SQLAlchemy-Utils constraint conflicts with rocky's upper constraints * bump lower constraint of cryptography * bump lower constraint of oslo.messaging * bump lower constraint of oslo.utils 3. lower-constraints In lower-constraints job lxml requires libxml2-dev and libxslt1-dev packages, so bindep.txt is extended with them. install_command needs to be added to lower-constraints tox target to work properly. 4. cinder-tempest-dsvm-lvm-lio-barbican Fix for overlapping CIDR issue in cinder-tempest-dsvm-lvm-lio-barbican is the same as in patch I068cf1e9618d305b5a9383c283bfa0f120bfe905. 5. pin nodeset to xenial for requirements-check job The default nodeset for zuul jobs is now ubuntu-focal, and requirements-check job fails on focal, because the mysql it contains is not compatible with the commands that is used in tools/test-setup.sh. This patch pins the nodeset to ubuntu-xenial for requirements-check job to make it pass. [1] https://github.com/PyCQA/bandit/releases/tag/1.6.3 [2] PyCQA/bandit#615 [3] PyCQA/bandit#663 [4] PyCQA/bandit#665 Change-Id: Ie597e778e3efa61bfd98eaaa92730b5050195e7a (cherry picked from commit a512bfc233fc76c4375388b8546ab9e60459e1d3)
- Loading branch information
Showing
7 changed files
with
22 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters