summaryrefslogtreecommitdiff
path: root/heat
diff options
context:
space:
mode:
authorGhanshyam Mann <gmann@ghanshyammann.com>2023-01-27 14:59:38 -0600
committerRodrigo Barbieri <rodrigo.barbieri@canonical.com>2023-02-21 16:05:09 +0000
commit604111b0ba07a0a55393745c5a0097cd675739cc (patch)
tree2e7875f86d97a85ce8f6ec97c72961b22e4b428d /heat
parent8e2286c9b2d9afb5c1750f2ccf7ec27e8a03e9cf (diff)
downloadheat-604111b0ba07a0a55393745c5a0097cd675739cc.tar.gz
Fix setting the tempest virtual env constraints env var
Heat upgrade script 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 this grenade script install the tempest with stable constraints but with master Tempest and as there is mismatch of constraints now with fasteners of stable branches. Below is failure of heat greande job on stable/yoga - https://zuul.opendev.org/t/openstack/build/3aaec4d59bb84068bb4d4428ea747cbd/log/controller/logs/grenade.sh_log.txt#3245 Similar way, role should set stable constraints only for the stable EM branch not for all otherwise it fail when constraints/requirements are bumped. - https://zuul.opendev.org/t/openstack/build/74f86b8097f44c35acaffdcfe41d9693 We should set/reset those constraint env var to master constraints if configuration tell to use the master constraints. Closes-Bug: #2003993 Change-Id: I024cd134577338fc1075e7742df7f006dc914646
Diffstat (limited to 'heat')
0 files changed, 0 insertions, 0 deletions