'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
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
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
This commit adds the releasenote to tag Tempest for Ussuri
and needed for version 24.0.0 to release.
Change-Id: Ic9c06f6457b1b4d13d57a86a7c7ed0d0dca0c082
Tempest and its plugin are very tightly coupled for testing
Upstream or Production Cloud. Due to its branchless model,
one of the challenges we faced/facing is to provide their
compatible version set.
Since Queens release and with operator request, we started
doing a coordinated release of plugins along with Tempest
which will be marked as the First compatible version for
that particular release.
For example https://releases.openstack.org/train/index.html#tempest-plugins
We test our stable branch with master version of Tempest &
plugins until it is moved to Extended Maintainance state.
One stable release is in EM state, Tempest officially declares
the end of support tag so that we can use that as the last compatible
version for that EM stable testing. But we do not have the correct
last compatible version from plugins which can be used for testing
the EM branch. It should be with hash from the master at the time
stable release is moved to EM not the hash when the stable release
was done otherwise it will be incompatible with Tempest.
We have faced and fixed many issue due to that during py2-drop work
where we have to pick and try all different versions from plugin to
make it work against EM testing.
Change-Id: I99a6df0a2c02e19efaf484fcd97b875887f08d8e
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.
BTW: some minor code refactor is done along with this patch.
Change-Id: I072bd2c86a7f50559e9e452dda3e1669fad3be00
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: I9840ea976d290a8fd22d8c3bae17db9ed42f629a
partially-implements: blueprint testcase-description
While loading data form plugin like tests,
config options etc we do not have enough logs
to debug if any plugins is missed.
It is difficult to debug in such cases where we do not
find config options registered by plugins,
For example: https://review.opendev.org/#/c/706785
Adding more logs to know what all data we are loading from
all plugins.
Change-Id: I09d2349a0e32c2265e6beb3dad4619ad33782a51
In case "TaggedBootDevicesTest.verify_device_metadata" "json.loads"
method returns an exception, catch it and return "False". This could
happen if, for example, the string to load is empty.
Because this function is called in an active wait loop, the content
string will be retrieved again and the check retried.
Change-Id: Id3a5b32f8ab197bcb1c59b5f6364dde4d8648eab
Closes-Bug: #1867904
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: I3d1634fab5826928a45bd47c18aba6fc32021075
partially-implements: blueprint testcase-description
Currently we rely on [service_available]ironic which
1) will give incorrect results in a mixed environment
2) doesn't work in grenade jobs
This change only allows ports to be DOWN when they have VNIC type
of baremetal.
Change-Id: If24913b7097c5252a214bb780fc786aa0c3f983b
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, however, we can extract info
from tempest code to create one, but, some testcases don't have
descriptions about what the testcases are testing, so, we can add
descrption for each testcase.
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: Id90d6fedccc84aa9548fba62b5926a75050ab443
partially-implements: blueprint testcase-description
This commit adds x/glare and x/tap-as-a-service to the BLACKLIST to
avoid sanity-job failures like following.
Failed Plugins: x/glare, x/tap-as-a-service,
+ [[ -n x/glare, x/tap-as-a-service, ]]
+ exit 1
It looks the root cause is related to pg_config installation but not
sure. So, this commit just blacklists them as a workaround.
Error: pg_config executable not found.
Change-Id: I03c6f01593b8e414b5e111d0e0c971ae156da715
This change adds a simple set of tests to exercise the stable device
rescue feature. A new [compute-feature-enabled]/stable_rescue
configurable is introduced to control when these tests are executed,
defaulting to False.
Change-Id: I0680fe4a6590aa3c4887d338a02b04fabfcdbb11
Microversion v2.73 was introduced in Nova by I46edd595e7417c58410648
changing the request responses of ``GET servers/{server_id}``, ``GET
/servers/detail``, ``POST /servers/{server_id}/action`` where the
action is rebuild and ``PUT servers/{server_id}``.
Change-Id: I8c800f6e280ec6fdf204d344124d994a25d0af19
- Fix noVNC failed TCs tempest.api.compute.servers.test_novnc.NoVNCConsoleTestJSON.test_novnc:
* Current noVNC request miss the / prefix in GET header in the websocket upgrade request.
* Current GET header GET ?token=xxx HTTP/1 can cause "HTTP/1.1 400 Bad Request" error.
* Fix the issue by adding / prefix and
# updated request format is: GET /?token=xxx HTTP/1.1 or GET /websockify HTTP/1.1
Change-Id: I38a91b8e293e39625d08073e2b898451b6126ecb
