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
Since setuptools v54.1.0[1], the parmeters with dash have been
deprecated in favor of the new parameters with underscore.
This change updates the parameters accordingly to avoid the warnings
like the example below.
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: Ica879c31574060471fb22c53761e6d4549a05db2
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 is kind of a race condition issue, Tempest is doing a wait and check
when it is trying to delete a cluster. However, at the very end of the cluster
deletion process, a cluster GET request may get a HTTP 400 error which
will cause the Tempest case failed. This HTTP 400 exception reported
by a cluster GET request should be caught and take cluster as still existing.
Task: 40120
Story: 2007833
Change-Id: Ic97abf8d4d584f35b18bff9eab5d3e5ac80c0f02
Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Disable openstackdocs_auto_name to use 'project' variable as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: I54eee940d3c787fddc1278619981d7a90310fbd0
Update docs building, cleanup a bit:
* Switch to sphinx-build
* Update requirements for Sphinx and openstackdocstheme for
python 3, create doc/requirements.txt
* Remove unneeded doc and translation sections from setup.cfg
* Remove install_command, it's unneeded, the default is fine.
* Move constraints into deps, use TOX_CONSTRAINTS instead of
obsolete UPPER_CONSTRAINTS
* Update to hacking 3.0, fix problems found
Change-Id: I76fe5602928bede439133993b0d85669228f25ed
--
Bump the openstackdocstheme extension to 1.20
Some options are now automatically configured by the version 1.20:
- project
- html_last_updated_fmt
- latex_engine
- latex_elements
- version
- release.
Ic9207bb8d3e602dd71cc4c7cefde739130f3d48b
--
Blacklist sphinx 2.1.0 (autodoc bug)
See https://github.com/sphinx-doc/sphinx/issues/6440 for upstream details
Ia029f66cfde96d97754e38b5278f1b24081a09e0
--
tox: Keeping going with docs
1. Sphinx 1.8 introduced [1] the '--keep-going' argument which, as its name
suggests, keeps the build running when it encounters non-fatal errors.
This is exceptionally useful in avoiding a continuous edit-build loop
when undertaking large doc reworks where multiple errors may be
introduced.
2. Remove the py27 from tox since magnum already drop support python 2.7
[1] https://github.com/sphinx-doc/sphinx/commit/e3483e9b045
I6e713b51cf9fac87e696fdfce8156f656a0f1df5
--
Change-Id: I53800a688fae3ba9cc551b0ceffe96938f2df59d
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
In case the cluster could be deleted immediately after the creation
failure, there is no chance to see the reason for debugging purpose.
Change-Id: I627f5b8bef3bc8fef694837cd7f037dc01885b53
Fix the test-requirements.txt which was broken by
https://review.opendev.org/657890 adding a cap on Sphinx on Python 2.
Change-Id: I1971495e9ebcebfd5950da4da17b555ddafe56c4
For some reason if sitepackages is enabled, tox does not install
tempest in py2. Do not use sitepackages since we install tempest from
pip anyway.
Change-Id: I7c2fa70e03e6478ddc8d640ca0f117a7b88d2207
- This fix is primarily focused on using existing cluster template
use case.
- Rename 'keypair_id' to 'keypair_name' in the magnum tempest config.
- Add 'cluster_template_id' and 'cluster_creation_timeout' config
options.
- Move the cluster template and keypair to the class-scoped resources.
Change-Id: Ib5260757e373ce545ca6900acf8871b6d96dcfb8
The plugin defines a 'magnum' option in the '[service_available]' group
but does not respect it, so if the plugin is installed but
[service_available]/magnum=false, the tests will still run unless
blacklisted. This patch corrects the issue by defining the tempest
skip_checks class method. This also requires using the correct tempest
base class as recommended in the tempest guide[1].
[1] https://docs.openstack.org/tempest/latest/write_tests.html
Change-Id: I6b9a8f802129fa800d9f4a3eadd8943962c951c0
Zuul