As 2023.1 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: I6437f79587ac28c7926f995ba64ddd5c9fa32cdd
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: Ie6ae6d3961d9dba8701e8b6f02475953db9c19da
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.
Also fixing the zuul config error.
[1] https://governance.openstack.org/tc/goals/selected/migrate-ci-jobs-to-ubuntu-jammy.html
Change-Id: Ib5d3dcf53b091fa68dee23b3ed9c0b8278e6ded8
The 'all-plugin' tox environment was deprecated by this patch [1].
Instead of the 'all-plugin' it is recommended to use the 'all' tox
environment.
This patch removes any reference to 'all-plugin' tox environment and
updates the documentation so that the installation steps work with
the 'all' venv.
[1] https://review.opendev.org/c/openstack/tempest/+/543974
Change-Id: I693e4a106f11e0cadac369fbc186e54ffff13d41
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
and stable/victoria job.
[1] https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: I550f33a18cc8318d97072115e0df1462821ecb0e
We have stable/victoria, stable/wallaby, and
stable/victoria released so we should add their job on
master gate to keep branchless tempest plugins compatible
to those branch.
This also removes the stable/train|stein job as thare are in EM
state now.
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: I9440ed27823193054fdd3e0a4ff7785fadca8d24
We need to specify doc requirements in doc/requirements.txt
to avoid problems with the pip resolver [1] for the release team [2][3].
Removing specific doc requirements from test-requirements.txt.
The problem here is that this repos haven't doc/requirements.txt file
and by default in this case zuul will use the test-requirements.txt file
to pull requirements [4].
This requirements file contains extra requirements like flake8 that
collided with those allowed in our job environment and so the new pip
resolver fails to install these requirements and the job exits in error.
This project meet the conditions leading to the bug.
/!\/!\/!\
Notice that I voluntarily added the doc directory even if no docs
are generated here because zuul will try to pull this requirements from
there first and the contained requirements are needed for reno but AFAIK
the releasenotes dir is ignored by zuul. c.f [4] for further details.
/!\/!\/!\
[1] http://lists.openstack.org/pipermail/release-job-failures/2021-January/001500.html
[2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019611.html
[3] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.html
[4] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tasks/main.yaml#L36
Change-Id: If0c66938ff1b505aba53d17293ff70612a3bd889
* Replace .testr.conf by .stestr.conf for migration and update
.gitignore and test-requirements.txt file accordingly
* Use py3 as the default runtime for tox
* The patch bumps min version of tox to 3.18.0 python in order to
replace tox's whitelist_externals by allowlist_externals option
* Updated ostestr occurances to stestr`
Change-Id: Iacc4e5054deb6ef832085d131c933e48e418bf1b
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove python 2.7 stanza from setup.py
- Remove obsolete sections from setup.cfg
- Update classifiers
- Use newer openstackdocstheme and Sphinx versions
- Remove install_command from tox.ini, the default is fine;
move constraints into deps
- Remove Babel from requirements, it's not needed for running;
remove babel.cfg likewise
- Use TOX_CONSTRAINTS_FILE, UPPER_CONSTRAINTS_FILE is obsolete
- update hacking to version 3.0
Change-Id: Ibcb7be4fd057b24147b7b562302ea362ad8c71b3
Supported stable branches in maintenance state
(stein, train, ussuri) 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].
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: I31798ce47063a55e6ef29d713dc156c2d873e3cb
Retrieve max api version at client creation and skip tests that require
higher api versions than supported.
Change-Id: I1d099157966bc73e6d104f7d293f4a0e30180662
This was hiding a bug with flavor_id. Make sure we
delete the cluster so that it will always fail gracefully.
In addition we also stop re-using the same private network
for cluster tests and instead create custom networks to
prevent race conditions between tests.
* Add a small retry for logic for deleting subnets and networks.
* Add override to network name to allow for randomized names.
Change-Id: Ibcf1b25bc6e5e3a54678646a397dc1c41b1d29af
There is no garuantee that content-length is set when
the payload is empty. It is also not a required field for
HTTP Status 204 (No Content) or DELETE.
Change-Id: Ifdd7cdef3a214a1153563c12e349dda9f179a2ad
Introduced a new configuration variable to set the
supported health policy version that is used to
help determine if we can run the health related
tests.
Change-Id: I025aada17db6900d3e4328d5c09890e4f260f4d6
Curly quotes(Chinese punctuation) usually input from Chinese input method.
When read from english context, it makes some confusion.
Change-Id: I8b96ee793eee8a8802cd9bd3993714768df27cb7
Ghanshyam Mann