Update git submodules
* Update grenade from branch 'master' to a8cbe6d1a9c2aafd8294d8bcf342410d6451e97f - Merge "Fix setting the tempest virtual env constraints env var" - Fix setting the tempest virtual env constraints env var Grenade set the env var TOX_CONSTRAINTS_FILE/UPPER_CONSTRAINTS_FILE which are used to use the constraints during Tempest virtual env installation. Those env var are set to non-master constraint when we need to use non-master constraints but when we need to use the master constraints we do not set/reset them point to master constraints. This create the issue when grenade script install the tempest second time on new devstack where we need to use master constraints but env var TOX_CONSTRAINTS_FILE/UPPER_CONSTRAINTS_FILE set previously in tempest installation in old devstack point to the stable constraints. One case where it started failing when we tried to pin the stable/wallaby with Tempest 29.0.0 - https://review.opendev.org/c/openstack/devstack/+/871782 and stable/xena grenade job failed (stable/xena use master tempest and supposed to use master constraints) - https://zuul.opendev.org/t/openstack/build/fb7b2a8b562c42bab4c741819f5e9732/log/controller/logs/grenade.sh_log.txt#16641 We should set/reset those constraint env var to master constraints if configuration tell to use the master constraints. Closes-Bug: #2003993 Change-Id: I8c623008292f3b2dd2cd6d596feea552194acd89
This commit is contained in:
parent
b7532a275b
commit
eb8127c8a6
2
grenade
2
grenade
|
@ -1 +1 @@
|
|||
Subproject commit 3877df6af1f5556d9960b6412e6e2011b19f5d49
|
||||
Subproject commit a8cbe6d1a9c2aafd8294d8bcf342410d6451e97f
|
Loading…
Reference in New Issue