Tempest virtual env constraints env variable not reset when using master constraints
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devstack |
Fix Released
|
Undecided
|
Unassigned | ||
grenade |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
In Devstack and grenade we do set the env var TOX_CONSTRAINTS
- https:/
- https:/
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 running the grenade job where we run Tempest on the old devstack as well as in the new devstack. When tempest is installed on old devstack then old tempest is used and it sets these env var to stable/<branch> constraints (this is the case when old devstack (the stable branch is in EM phase) uses the old tempest not the master tempest), all good till now. But the problem comes when in the same grenade script run upgrade-tempest install the master tempest (when new devstack branches are in the 'supported' phase and use the master tempest means) and are supposed to use the master constraints. But the TOX_CONSTRAINTS
This happened when we tried to pin the stable/wallaby with Tempest 29.0.0
- https:/
and table/xena grenade job failed (stable/xena use master tempest and supposed to use master constraints)
- https:/
Fix is simple, we need to set/reset those constraint env var to master constraints if configuration tell devstack to use the master constraints.
OpenStack Infra (hudson-openstack) wrote : Fix proposed to devstack (master) | #1 |
Changed in devstack: | |
status: | New → In Progress |
OpenStack Infra (hudson-openstack) wrote : Fix proposed to devstack (stable/zed) | #2 |
Fix proposed to branch: stable/zed
Review: https:/
OpenStack Infra (hudson-openstack) wrote : Fix proposed to devstack (stable/yoga) | #3 |
Fix proposed to branch: stable/yoga
Review: https:/
OpenStack Infra (hudson-openstack) wrote : Fix proposed to devstack (stable/xena) | #4 |
Fix proposed to branch: stable/xena
Review: https:/
OpenStack Infra (hudson-openstack) wrote : Fix proposed to grenade (master) | #5 |
Fix proposed to branch: master
Review: https:/
Changed in grenade: | |
status: | New → In Progress |
OpenStack Infra (hudson-openstack) wrote : Fix proposed to grenade (stable/zed) | #6 |
Fix proposed to branch: stable/zed
Review: https:/
OpenStack Infra (hudson-openstack) wrote : Fix proposed to grenade (stable/yoga) | #7 |
Fix proposed to branch: stable/yoga
Review: https:/
OpenStack Infra (hudson-openstack) wrote : Fix proposed to grenade (stable/xena) | #8 |
Fix proposed to branch: stable/xena
Review: https:/
OpenStack Infra (hudson-openstack) wrote : Fix proposed to grenade (stable/wallaby) | #9 |
Fix proposed to branch: stable/wallaby
Review: https:/
OpenStack Infra (hudson-openstack) wrote : Fix merged to devstack (master) | #10 |
Reviewed: https:/
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 7fe998109bda8cd
Author: Ghanshyam Mann <email address hidden>
Date: Thu Jan 26 22:28:07 2023 -0600
Fix setting the tempest virtual env constraints env var
Devstack set the env var TOX_CONSTRAINTS
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 running the grenade
job where we run Tempest on the old devstack as well as in the new devstack.
When tempest is installed on old devstack then old tempest is used and it sets
these env var to stable/<branch> constraints (this is the case when old devstack
(the stable branch is in EM phase) uses the old tempest not the master tempest),
all good till now. But the problem comes when in the same grenade script run
upgrade-tempest install the master tempest (when new devstack branches are in
the 'supported' phase and use the master tempest means) and are supposed to use
the master constraints. But the TOX_CONSTRAINTS
var set by old tempest is used by the tempest and due to a mismatch in constraints
it fails.
This happened when we tried to pin the stable/wallaby with Tempest 29.0.0
- https:/
and table/xena grenade job failed (stable/xena use master tempest and supposed
to use master constraints)
- https:/
We should set/reset those constraint env var to master constraints if configuration
tell devstack to use the master constraints.
[1] https:/
Closes-Bug: #2003993
Change-Id: I5e938139b47f44
Changed in devstack: | |
status: | In Progress → Fix Released |
OpenStack Infra (hudson-openstack) wrote : Fix merged to devstack (stable/zed) | #11 |
Reviewed: https:/
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/zed
commit 30a7d790b6bf45b
Author: Ghanshyam Mann <email address hidden>
Date: Thu Jan 26 22:28:07 2023 -0600
Fix setting the tempest virtual env constraints env var
Devstack set the env var TOX_CONSTRAINTS
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 running the grenade
job where we run Tempest on the old devstack as well as in the new devstack.
When tempest is installed on old devstack then old tempest is used and it sets
these env var to stable/<branch> constraints (this is the case when old devstack
(the stable branch is in EM phase) uses the old tempest not the master tempest),
all good till now. But the problem comes when in the same grenade script run
upgrade-tempest install the master tempest (when new devstack branches are in
the 'supported' phase and use the master tempest means) and are supposed to use
the master constraints. But the TOX_CONSTRAINTS
var set by old tempest is used by the tempest and due to a mismatch in constraints
it fails.
This happened when we tried to pin the stable/wallaby with Tempest 29.0.0
- https:/
and table/xena grenade job failed (stable/xena use master tempest and supposed
to use master constraints)
- https:/
We should set/reset those constraint env var to master constraints if configuration
tell devstack to use the master constraints.
[1] https:/
Closes-Bug: #2003993
Change-Id: I5e938139b47f44
(cherry picked from commit 7fe998109bda8cd
tags: | added: in-stable-zed |
OpenStack Infra (hudson-openstack) wrote : Fix merged to devstack (stable/yoga) | #12 |
Reviewed: https:/
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/yoga
commit febdb122e46ad22
Author: Ghanshyam Mann <email address hidden>
Date: Thu Jan 26 22:28:07 2023 -0600
Fix setting the tempest virtual env constraints env var
Devstack set the env var TOX_CONSTRAINTS
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 running the grenade
job where we run Tempest on the old devstack as well as in the new devstack.
When tempest is installed on old devstack then old tempest is used and it sets
these env var to stable/<branch> constraints (this is the case when old devstack
(the stable branch is in EM phase) uses the old tempest not the master tempest),
all good till now. But the problem comes when in the same grenade script run
upgrade-tempest install the master tempest (when new devstack branches are in
the 'supported' phase and use the master tempest means) and are supposed to use
the master constraints. But the TOX_CONSTRAINTS
var set by old tempest is used by the tempest and due to a mismatch in constraints
it fails.
This happened when we tried to pin the stable/wallaby with Tempest 29.0.0
- https:/
and table/xena grenade job failed (stable/xena use master tempest and supposed
to use master constraints)
- https:/
We should set/reset those constraint env var to master constraints if configuration
tell devstack to use the master constraints.
[1] https:/
Closes-Bug: #2003993
Change-Id: I5e938139b47f44
(cherry picked from commit 7fe998109bda8cd
(cherry picked from commit 30a7d790b6bf45b
tags: | added: in-stable-yoga |
OpenStack Infra (hudson-openstack) wrote : Fix merged to devstack (stable/xena) | #13 |
Reviewed: https:/
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/xena
commit cb891834beb0f3b
Author: Ghanshyam Mann <email address hidden>
Date: Thu Jan 26 22:28:07 2023 -0600
Fix setting the tempest virtual env constraints env var
Devstack set the env var TOX_CONSTRAINTS
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 running the grenade
job where we run Tempest on the old devstack as well as in the new devstack.
When tempest is installed on old devstack then old tempest is used and it sets
these env var to stable/<branch> constraints (this is the case when old devstack
(the stable branch is in EM phase) uses the old tempest not the master tempest),
all good till now. But the problem comes when in the same grenade script run
upgrade-tempest install the master tempest (when new devstack branches are in
the 'supported' phase and use the master tempest means) and are supposed to use
the master constraints. But the TOX_CONSTRAINTS
var set by old tempest is used by the tempest and due to a mismatch in constraints
it fails.
This happened when we tried to pin the stable/wallaby with Tempest 29.0.0
- https:/
and table/xena grenade job failed (stable/xena use master tempest and supposed
to use master constraints)
- https:/
We should set/reset those constraint env var to master constraints if configuration
tell devstack to use the master constraints.
Making openstacksdk-
failing 100% on stable/xena
- https:/
[1] https:/
Closes-Bug: #2003993
Change-Id: I5e938139b47f44
(cherry picked from commit 7fe998109bda8cd
(cherry picked from commit 30a7d790b6bf45b
(cherry picked from commit febdb122e46ad22
tags: | added: in-stable-xena |
OpenStack Infra (hudson-openstack) wrote : Fix proposed to devstack (stable/wallaby) | #14 |
Fix proposed to branch: stable/wallaby
Review: https:/
OpenStack Infra (hudson-openstack) wrote : Fix merged to devstack (stable/wallaby) | #15 |
Reviewed: https:/
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/wallaby
commit f5e83ee14a36df1
Author: Ghanshyam Mann <email address hidden>
Date: Thu Jan 26 22:28:07 2023 -0600
Fix setting the tempest virtual env constraints env var
Devstack set the env var TOX_CONSTRAINTS
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 running the grenade
job where we run Tempest on the old devstack as well as in the new devstack.
When tempest is installed on old devstack then old tempest is used and it sets
these env var to stable/<branch> constraints (this is the case when old devstack
(the stable branch is in EM phase) uses the old tempest not the master tempest),
all good till now. But the problem comes when in the same grenade script run
upgrade-tempest install the master tempest (when new devstack branches are in
the 'supported' phase and use the master tempest means) and are supposed to use
the master constraints. But the TOX_CONSTRAINTS
var set by old tempest is used by the tempest and due to a mismatch in constraints
it fails.
This happened when we tried to pin the stable/wallaby with Tempest 29.0.0
- https:/
and table/xena grenade job failed (stable/xena use master tempest and supposed
to use master constraints)
- https:/
We should set/reset those constraint env var to master constraints if configuration
tell devstack to use the master constraints.
Making openstacksdk-
failing 100% on <=stable/xena, depends-On fix that
Depends-On: https:/
[1] https:/
Closes-Bug: #2003993
Change-Id: I5e938139b47f44
(cherry picked from commit 7fe998109bda8cd
(cherry picked from commit 30a7d790b6bf45b
(cherry picked from commit febdb122e46ad22
(cherry picked from commit cb891834beb0f3b
tags: | added: in-stable-wallaby |
OpenStack Infra (hudson-openstack) wrote : Fix merged to grenade (master) | #16 |
Reviewed: https:/
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 01e143de49182da
Author: Ghanshyam Mann <email address hidden>
Date: Thu Jan 26 23:12:59 2023 -0600
Fix setting the tempest virtual env constraints env var
Grenade set the env var TOX_CONSTRAINTS
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_
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:/
and stable/xena grenade job failed (stable/xena use master tempest and supposed
to use master constraints)
- https:/
We should set/reset those constraint env var to master constraints if configuration
tell to use the master constraints.
Closes-Bug: #2003993
Change-Id: I8c623008292f3b
Changed in grenade: | |
status: | In Progress → Fix Released |
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/heat 20.0.0.0rc1 | #17 |
This issue was fixed in the openstack/heat 20.0.0.0rc1 release candidate.
OpenStack Infra (hudson-openstack) wrote : Fix merged to grenade (stable/zed) | #18 |
Reviewed: https:/
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/zed
commit e17b3a2119f55d7
Author: Ghanshyam Mann <email address hidden>
Date: Thu Jan 26 23:12:59 2023 -0600
Fix setting the tempest virtual env constraints env var
Grenade set the env var TOX_CONSTRAINTS
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_
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:/
and stable/xena grenade job failed (stable/xena use master tempest and supposed
to use master constraints)
- https:/
We should set/reset those constraint env var to master constraints if configuration
tell to use the master constraints.
Closes-Bug: #2003993
Change-Id: I8c623008292f3b
(cherry picked from commit 01e143de49182da
OpenStack Infra (hudson-openstack) wrote : Fix proposed to grenade (master) | #19 |
Fix proposed to branch: master
Review: https:/
OpenStack Infra (hudson-openstack) wrote : Fix proposed to grenade (stable/2023.1) | #20 |
Fix proposed to branch: stable/2023.1
Review: https:/
OpenStack Infra (hudson-openstack) wrote : Fix proposed to grenade (stable/zed) | #21 |
Fix proposed to branch: stable/zed
Review: https:/
OpenStack Infra (hudson-openstack) wrote : Fix proposed to grenade (stable/yoga) | #22 |
Fix proposed to branch: stable/yoga
Review: https:/
OpenStack Infra (hudson-openstack) wrote : Fix proposed to grenade (stable/xena) | #23 |
Fix proposed to branch: stable/xena
Review: https:/
OpenStack Infra (hudson-openstack) wrote : Fix merged to grenade (master) | #24 |
Reviewed: https:/
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 4c9c059883158fd
Author: Ghanshyam Mann <email address hidden>
Date: Thu Mar 30 20:58:04 2023 -0500
Fix tempest venv constraints for target branch tempest run
We fixed the tempest venv constraints setting for tempest test run
on base branch but forgot to do the same for target branch test run.
It cause issue when base and target branch have different Tempest
and constraints to use (for example stable/wallaby use old tmepest
and stable/wallaby constraints but stable/xena use tempest master
and master constraints), in such cases we need to set proper constraints
defined in devstack and then run tempest.
We do not see this issue as none of the job run tempest on target except
heat (https:/
I reproduced the issue in grenade stable/xena by enaling the tempest run
on target:
- https:/
- https:/
Closes-Bug: 2003993
Change-Id: I05fcdb5045a339
OpenStack Infra (hudson-openstack) wrote : Fix merged to grenade (stable/2023.1) | #25 |
Reviewed: https:/
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/2023.1
commit 62ea9b6ba35ae28
Author: Ghanshyam Mann <email address hidden>
Date: Thu Mar 30 20:58:04 2023 -0500
Fix tempest venv constraints for target branch tempest run
We fixed the tempest venv constraints setting for tempest test run
on base branch but forgot to do the same for target branch test run.
It cause issue when base and target branch have different Tempest
and constraints to use (for example stable/wallaby use old tmepest
and stable/wallaby constraints but stable/xena use tempest master
and master constraints), in such cases we need to set proper constraints
defined in devstack and then run tempest.
We do not see this issue as none of the job run tempest on target except
heat (https:/
I reproduced the issue in grenade stable/xena by enaling the tempest run
on target:
- https:/
- https:/
Closes-Bug: 2003993
Change-Id: I05fcdb5045a339
(cherry picked from commit 4c9c059883158fd
OpenStack Infra (hudson-openstack) wrote : Fix merged to grenade (stable/zed) | #26 |
Reviewed: https:/
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/zed
commit ff45be406ae3019
Author: Ghanshyam Mann <email address hidden>
Date: Thu Mar 30 20:58:04 2023 -0500
Fix tempest venv constraints for target branch tempest run
We fixed the tempest venv constraints setting for tempest test run
on base branch but forgot to do the same for target branch test run.
It cause issue when base and target branch have different Tempest
and constraints to use (for example stable/wallaby use old tmepest
and stable/wallaby constraints but stable/xena use tempest master
and master constraints), in such cases we need to set proper constraints
defined in devstack and then run tempest.
We do not see this issue as none of the job run tempest on target except
heat (https:/
I reproduced the issue in grenade stable/xena by enaling the tempest run
on target:
- https:/
- https:/
Closes-Bug: 2003993
Change-Id: I05fcdb5045a339
(cherry picked from commit 4c9c059883158fd
(cherry picked from commit 62ea9b6ba35ae28
OpenStack Infra (hudson-openstack) wrote : Fix merged to grenade (stable/yoga) | #27 |
Reviewed: https:/
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/yoga
commit cd782d27d56b0d0
Author: Ghanshyam Mann <email address hidden>
Date: Thu Mar 30 20:58:04 2023 -0500
Fix tempest venv constraints for target branch tempest run
We fixed the tempest venv constraints setting for tempest test run
on base branch but forgot to do the same for target branch test run.
It cause issue when base and target branch have different Tempest
and constraints to use (for example stable/wallaby use old tmepest
and stable/wallaby constraints but stable/xena use tempest master
and master constraints), in such cases we need to set proper constraints
defined in devstack and then run tempest.
We do not see this issue as none of the job run tempest on target except
heat (https:/
I reproduced the issue in grenade stable/xena by enaling the tempest run
on target:
- https:/
- https:/
Extra on backport:
We need heat fixes to pass the heat multinode grenade job
Depends-On: https:/
Depends-On: https:/
Closes-Bug: 2003993
Change-Id: I05fcdb5045a339
(cherry picked from commit 4c9c059883158fd
(cherry picked from commit 62ea9b6ba35ae28
(cherry picked from commit ff45be406ae3019
OpenStack Infra (hudson-openstack) wrote : Fix merged to grenade (stable/xena) | #28 |
Reviewed: https:/
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/xena
commit 6c3167112866bd6
Author: Ghanshyam Mann <email address hidden>
Date: Thu Mar 30 20:58:04 2023 -0500
Fix tempest venv constraints for target branch tempest run
We fixed the tempest venv constraints setting for tempest test run
on base branch but forgot to do the same for target branch test run.
It cause issue when base and target branch have different Tempest
and constraints to use (for example stable/wallaby use old tmepest
and stable/wallaby constraints but stable/xena use tempest master
and master constraints), in such cases we need to set proper constraints
defined in devstack and then run tempest.
We do not see this issue as none of the job run tempest on target except
heat (https:/
I reproduced the issue in grenade stable/xena by enaling the tempest run
on target:
- https:/
- https:/
Extra on backport:
We need heat fixes to pass the heat multinode grenade job
Depends-On: https:/
Depends-On: https:/
Closes-Bug: 2003993
Change-Id: I05fcdb5045a339
(cherry picked from commit 4c9c059883158fd
(cherry picked from commit 62ea9b6ba35ae28
(cherry picked from commit ff45be406ae3019
(cherry picked from commit cd782d27d56b0d0
OpenStack Infra (hudson-openstack) wrote : Change abandoned on grenade (stable/yoga) | #29 |
Change abandoned by "Ghanshyam <email address hidden>" on branch: stable/yoga
Review: https:/
Reason: fixed in https:/
OpenStack Infra (hudson-openstack) wrote : Change abandoned on grenade (stable/xena) | #30 |
Change abandoned by "Ghanshyam <email address hidden>" on branch: stable/xena
Review: https:/
Reason: fixed in https:/
OpenStack Infra (hudson-openstack) wrote : Change abandoned on grenade (stable/wallaby) | #31 |
Change abandoned by "Ghanshyam <email address hidden>" on branch: stable/wallaby
Review: https:/
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/heat 17.0.2 | #32 |
This issue was fixed in the openstack/heat 17.0.2 release.
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/heat 18.0.1 | #33 |
This issue was fixed in the openstack/heat 18.0.1 release.
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/heat 19.0.1 | #34 |
This issue was fixed in the openstack/heat 19.0.1 release.
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/heat wallaby-eom | #35 |
This issue was fixed in the openstack/heat wallaby-eom release.
Fix proposed to branch: master /review. opendev. org/c/openstack /devstack/ +/871942
Review: https:/