stable/wallaby is in EM state. As Tempest and
plugins masters does not support EM stable branches,
QA team is pinning tempest in devstack stable/wallaby
tesitng[1]. With that we do not need to test the
stable/wallaby jobs on master gate
[1] https://review.opendev.org/c/openstack/devstack/+/871782
Change-Id: I15afdc2d8e472e8ad93192155900aa10a4b8439f
As zed is released, we should add its job on master
gate to keep branchless tempest plugins compatible
to stable branch.
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: I1406a1bf99861315001a573a7d187957bab37682
In 2023.1 cycle. we are moving the default distro
version of Ubuntu to Jammy (22.04)[1] so we need to pin
the nodeset for stable branch job in master gate so that
they continue run on their supporting distro version which is
Ubuntu Focal since stable/victoria.
[1] https://governance.openstack.org/tc/goals/selected/migrate-ci-jobs-to-ubuntu-jammy.html
Change-Id: I0f29d5989b82020bee585f7075915c7c87c7dfc3
stable/victoria is in EM state and Tempest is pinned
there so we do not need to test the stable/victoria
jobs on master gate.
Change-Id: Iac14d4874dd455ebfcafa777de1d720d020624b6
We have stable/yoga released and stable/ussuri is in
'Extended Maintenance' state. Current 'Maintained'
stable branches are yoga, xena, wallaby, and victoria.
As per tempest stable branch testing policy[1], adding the
newly released stable/yoga job and remove the EM stable/ussuri
job.
[1] https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: Ic283d95deebfb71236941f369fae1f0c72136881
Supported stable branches in maintenance state
(ussuri, victoria, wallaby, xena) use the Tempest and plugins master
version for their testing. To make sure master version (new
tests or any changes) is compatible with stable branch testing,
we need to add the stable branches job on the plugins master gate.
Tempest and many other plugins are already testing the stable
branches in same way[1].
We are adding Victoria onwards jobs and ussuri one which is failing
and might need more fixes can be added separatly.
Ussuri onwards, Tempest or plugins are py3 only, so we are
running only python3 version of stable jobs
Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
[1] e8f1876aa6/.zuul.yaml (L646)
Change-Id: If92a78f10935b374de5508df14b428d0aa5e24ce
Since [1] is merged, quota in glance is enabled but limit is set to
1GB by default and this is too small for Magnum jobs using Fedora
images.
This change extends the limit to fix the issue caused by that low
limit.
[1] https://review.opendev.org/c/openstack/devstack/+/788056
Depends-on: https://review.opendev.org/802413
Change-Id: Id741fafc7e1da2d4e180f0745cd4d4b367472f06
Tempest replaced the below rolevar for run-tempest role
- tempest_test_blacklist is replaced by tempest_test_exclude_list
- tempest_black_regex is replaced by tempest_exclude_regex
old name are still supported for compatiblity but we recommend
to switch to new one.
Depends-On: https://review.opendev.org/c/openstack/tempest/+/774835
Change-Id: I5d66e18757d516f8c761875bd2f824d0e839f1ac
Cluster creation fails on the CI due to an issue similar to what we've
seen before for another test (test_create_list_sign_delete_clusters).
Disable it for now.
story: 2007272
task: 38867
story: 2007851
task: 41443
Change-Id: Ie91fdfe71058b45c5fd1217920b8b5b993e47734
keeping magnum-tempest-plugin-tests-api job running on bionic nodeset till
https://storyboard.openstack.org/#!/story/2007732 is fixed
otherwise base devstack jobs switching to Focal will block
the gate.
Story: #2007865
Task: #40190
Change-Id: I78c8f92428efd27d604258f361077d909a27aa23
This commit defines magnum-tempest-plugin-tests-api job which uses the
new devstack-tempest as parent job recommended for running
Tempest tests in Zuul v3.
Story: 2007561
Task: 39470
Depends-on: https://review.opendev.org/#/c/721265
Change-Id: If7b77099a90d405e248c80777fa5e8b3612b5c2e
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I1735c09327eb2dac52fb6c153ea05168f572395b
Story: #2002586
Task: #24308
Ghanshyam Mann