support-policy section was renamed in
- https://review.opendev.org/#/c/725446/
but redirect for that was not correct. Fixing that
redirect.
Change-Id: Ia2921533c7a61bab4325a4a89b2b84f391e0aafd
Running verify_tempest_config, it complains with:
/opt/stack/tempest/tempest/cmd/verify_tempest_config.py:444:
DeprecationWarning: This method will be removed in future versions.
Use 'parser.read_file()' instead.
Use read_file.
Also, remove one extra use of six in this file.
Change-Id: Ia32df8e2be29bb0951efd08db9eed9e67d749e1f
The patch adds a new ansible role called tempest-cleanup which will
allow us to test tempest cleanup in the gate jobs.
Change-Id: I2cef2da6fee13e622da07b890da88850fe420152
Now we have more documents for plugins on stable release,
support and their testing policy. Let's prepare a
index page for it will be easy for plugins maintainer.
Also renaming the stable support policy section to have a clear
name.
Adding redirect links for moved documents.
Change-Id: I17a9a6e0e88605a0ee5047678d6ed168c31396ec
As Tempest and plugins master version is used to test the supported
stable branches, we need to test them on master gate.
Adding document for that so that we can test the stable branches
more consistently on plugins side too.
Change-Id: Ied3c6bb4032fd3740ae0d6d185e4a138fd335b02
Currently ceph job is n-v, if I remember
correctly it was kept n-v due to its stability.
But it is stable and voting on many projects. With
n-v it is hard to monitor it all the time.
let's make it voting and if any new tests failing we
can add that in the ceph blacklist in advance.
Example: https://review.opendev.org/#/c/724866/
Change-Id: Ic484d233b325c887f0a19f3ec06376d403beb964
We are doing this for downstream testing that use custom images
and in case you are not a cubs fan :)
Change-Id: I5860dc67233ce3135daf11b7901b93547ba1f30a
'grenade' is zuulv3 native job for py3 (because devstack is default to
py3 since Ussuri) which replace the old 'grenade-py3'
legacy job. 'grenade-py3' job is alias to the new zuulv3 native
'grenade' job but that is only for migration time. Later once
all switch to new job name, we will remvoe the 'grenade-py3' alias
job.
Change-Id: Iea355514ec7cc2a52ed5e88c356bcb1cdeadd639
Now we have stable/ussuri branch ready for devstack
and so does for all service projects.
This commit adds the Tempest testing for stable/ussuri
by adding new jobs running on stable/ussuri version of
openstack.
Depends-On: https://review.opendev.org/#/c/723605/
Change-Id: Ifa7887675d34ab8169347b69a8e1ff723b55e466
This change introduces tests for stable device rescue with boot from
volume instances using blank, image and snapshot based volumes.
Change-Id: Ic5e38c6da710e1e5fb40b186d8da537eef48b1a5
UPPER_CONSTRAINTS_FILE is deprecatedi[1], set the newer
TOX_CONSTRAINTS_FILE as well when interacting with other repos for the
transition.
Update internal use but not the tox.ini file, since users calling it
might use the old variable.
[1] https://zuul-ci.org/docs/zuul-jobs/python-roles.html#rolevar-tox.tox_constraints_file
Change-Id: Iea09402cf918a6978120a341950643185c94ec85
This is a follow-up of:
https://review.opendev.org/453144
and it fixes the last usage of the encryptor classes
which was introduced by https://review.opendev.org/472219
while the previous "clean-up" change was waiting to be merged.
Change-Id: I564d9f4d603c7f0dbfdde65dac1325c26fdff999
server rescue tests also create server without passing
the network to nova which further fail if more than one test network exists.
https://03399ed3bb928f8e37fb-954a4196d912d707c769d8596124df5e
.ssl.cf1.rackcdn.com/720042/1/check/nova-next/ba84dfc/testr_results.html
Change-Id: Ic9930172a1b6937cd038707afd4d0f6e3730efa1
Partial-Bug: #1844568
WHile releasing the new tag for Tempest, we modified the
constraint in tox to be used of stable/ussuri
- https://review.opendev.org/#/c/720578/
Now new tag is released and we can bring back the master
constraint in tox.ini so that Tempest master us master constraint.
Change-Id: Ie17d4830cac1902371123c8acb4d3106ba2fd300
We are going to releease Tempest new tag to declare the start of
support for stable/ussuri. So that new tag use stable/ussuri
constraint in the tox env.
For example: if anyone use Tempest 24.0.0 in future say 1 year later then
tox env also should use the ussuri contstraint for compatibility instead
master.
These need to be move back to master constraint once release is done.
By using master constraint in tox for all the old tag is problem and
we faced the issue of constraint incompatibility due to that and we
have to work around it all over the devstack, tempest role, grenade to
set the stable constraint cia env var.
- I4268049ff91e5527e4b95fd8a70fa53ba27d56ed
Change-Id: I39e3e23a85a9abc1eda6848a6f4af77540cb81b6
When Tempest is used in customer site, often we are required to
provide a testcase list including testcase names and descriptions.
Now no this kind of doc is available, so we can add descriptions
with the format of doc string for every testcase, so later we
can generata such a testcase description list.
There are hundreds of testcases missing descriptions, so we can
add them gradually, and limit the modified files in one patch
for the convenience of reviewing.
Change-Id: I1467cd41abbafc0622f3c032bba4213f4f09c18d
partially-implements: blueprint testcase-description
When Tempest is used in customer site, often we are required to
provide a testcase list including testcase names and descriptions.
Now no this kind of doc is available, so we can add descriptions
with the format of doc string for every testcase, so later we
can generata such a testcase description list.
There are hundreds of testcases missing descriptions, so we can
add them gradually, and limit the modified files in one patch
for the convenience of reviewing.
Change-Id: I63092a296b428a8d9da1960e8f082f594a8d28ff
partially-implements: blueprint testcase-description
This commit adds the releasenote to tag Tempest for Ussuri
and needed for version 24.0.0 to release.
Change-Id: Ic9c06f6457b1b4d13d57a86a7c7ed0d0dca0c082
Add all the scenario network tests which mainly involves network
and compute.
Also, fix an incorrect entry which most likely has no matches
(test_network_v6.py test_security_groups_basic_ops.py are different
files at the same level).
Change-Id: I936f263b4c1d96689d276ecfcf25ef1560d66ced
