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. With that we do not need to test the
stable/wallaby jobs on master gate
Since setuptools v54.1.0, 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
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, adding the
newly released stable/yoga job and remove the EM stable/ussuri
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.
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:
 e8f1876aa6/.zuul.yaml (L646)
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.
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.
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.
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.
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
* Update to hacking 3.0, fix problems found
Bump the openstackdocstheme extension to 1.20
Some options are now automatically configured by the version 1.20:
Blacklist sphinx 2.1.0 (autodoc bug)
See https://github.com/sphinx-doc/sphinx/issues/6440 for upstream details
tox: Keeping going with docs
1. Sphinx 1.8 introduced  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
2. Remove the py27 from tox since magnum already drop support python 2.7
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.
- This fix is primarily focused on using existing cluster template
- Rename 'keypair_id' to 'keypair_name' in the magnum tempest config.
- Add 'cluster_template_id' and 'cluster_creation_timeout' config
- Move the cluster template and keypair to the class-scoped resources.
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.