jsonschema.compat module is not a public interface anymore and
it got removed in version > 3.2.0
The compat module was a helper for py2/3 compatibility [1].
As Tempest is full py3 now, we can rework the whole
if-condition and let the timeutils to handle any wrong format.
[1] https://github.com/Julian/jsonschema/blob/v3.2.0/jsonschema/compat.py
Closes-Bug: #1946321
Change-Id: Ia78c19c06cfb712b1b8d0aff457fd2f91144dc07
Let's try to unskip test_create_object_with_transfer_encoding
and see if it's still failing. The commit marks the test as
unstable so that it doesn't fail a check/gate job in case the
test fails again.
Related-Bug: #1905432
Change-Id: I84ad0a3a699cc0c04b2ce173edceb1df46f8c7a1
The local IP is replaced with a wrong and irregular value
if tested with IPv6. This patch fixes this, replacing the
netloc with the right IPv6 localhost value.
Closes-Bug: 1944728
Change-Id: Icb3668abebb4821f1cf4824f4898abb2163e4d99
Now we have stable/xena branch ready for devstack
and so does for all service projects.
This commit adds the Tempest testing for stable/xena
by adding new jobs running on stable/xena version of
openstack.
Change-Id: If6f188aebe48f17d8a343c958cdeb5507421a40b
This reverts commit 0976ae4ee2. That
commit introduced a skip of MinBwAllocationPlacementTest tests if no
bandwidth allocation is possible to avoid failing these tests in OVN
jobs. However that is a wrong solutions as it would skip the test also
in OVS jobs if we regress the bandwidth inventory reporting in neutron
(or regress allocation candidate handling in placement).
A better fix is not to enable the tempest test flag on OVN jobs:
$TEMPEST_CONFIG:
network-feature-enabled:
qos_placement_physnet
The existing tests already skipped if this is not configured.
This also means that the generic tempest-* job definitions should not
configure the above flag as those tempest jobs will run by default with
OVN. So they are cleaned up along with the OVS specific neutron configuration.
This means that jobs that was inherit from tempest-multinode-full-py3
and tempest-full-py3 and reconfigre the job to run with OVS instead of
the default OVN needs to change to configure the OVS specific network
config and enable the qos tests. This will be done in project specific
patches.
The stable tempest jobs are OK as they are still running with OVS by
default.
Depends-On: https://review.opendev.org/c/openstack/neutron/+/806170
Change-Id: I13fd2dc023b806ac74ab5c8d86cc99f807f0f702
2 tests perfoming a volume and server snapshot weren't skipped
when the snapshot features were disabled:
CONF.volume_feature_enabled.snapshot
CONF.compute_feature_enabled.snapshot
Closes-Bug: #1938529
Change-Id: If7621e5ad982f43777ad3354d48ac8235420d1c6
The test was randomly failing which was most likely caused by
a race condition - the temporary module is not created at the
moment when the test tries to load it.
This commit moves the temp module creation into a setUp method.
Closes-Bug: #1918316
Change-Id: I5d5356200f531a06b2814205d65f20dc528cf046
In some cases (such as when using Ceph RADOSGW with a load-balancer)
the container (bucket) creation will be received by different backend
to the object creation triggering a subtle edge case.
The rgw handling the object creation request has (cached) knowledge
the bucket doesn't exist (it didn't a few seconds ago) and will (in
rgw) create it, at which point triggering a "409 BucketAlreadyExists"
code.
Detecting this and retrying (with a small delay) should reduce
instances of this failing.
Change-Id: Id88fb93dd1a48d046917e9168d623e53497ec83e
Tempest 29.0.0 has been released [1].
This commit adds a new page for 29.0.0 release notes and for
2 previous releases (as we forgot to add them before).
[1] https://review.opendev.org/c/openstack/releases/+/808035
Change-Id: I51e8906a89bae107a4fe162fcc785130edaa3565
While releasing a new tag for Tempest, we modified the
constraint in tox.ini so that they are set to xena instead of
master - https://review.opendev.org/c/openstack/tempest/+/808031
Now the new tag is released and we can bring back the master
constraint in tox.ini so that Tempest master uses master constraint.
Change-Id: Iaf9eaaf60ea3c2d15b1225f713364ebede25768a
We are going to release Tempest a new tag to declare the start of
support for stable/xena so the new tag should use stable/xena
constraint in the tox env.
For example: if anyone uses Tempest 29.0.0 in the future, say 1 year
later, then tox env also should use the xena contstraint instead
master for the compatibility.
These changes need to be moved back to master constraint once the
release is done. Using master constraint in tox.ini for all the older
tags is a problem and we faced the issue of constraint
incompatibility. Therefore, we have to work around it all over the
devstack, tempest, grenade and set the stable constraints via the
env var.
Change-Id: I2bbf550294e7873eb07598b204ccc8d63ff6b5eb
API microversions are inhertied in nature from features points
of view, means higher microversion will have all the features/
changes done in lower microversion.
In Tempest we write the microversion tests by capping
the min and max microversion so that they can request
the API with correct microversion.
But for non microversion tests we do not test if they are
run-able for all the configured microversion in Tempest config
file. To test it at some extend this commit adds a experimental
job to run the API tests (compute and volume) with 'latest'
microversion to know if that run successfully or need modification.
This job is experimental as now as I expect lot of test failure
with the 'latest' microversion and as we keep fixing those and all
the tests pass then we can move it to voting job in check/gate pipeline.
Change-Id: Ie840dd0997519d7e11a661853f9376f43c6e7905
"QoS Limit Bandwidth" APIs must be used in Octavia-Tempest-Plugin
to add missing QoS based tests.
Note: this patch fixes the "expected status" code for
Update Minimum Bandwidth, that was set to default 200 instead of 202.
Change-Id: I30d9d823c972e560a0a48e24e44fb16bcc353c5a
Currently tempest-ipv6-only job run on all the files change
present in /tools dir which is not required. For example
when we update the tempest plugin sanity scripts present in
/tools dir then this job run which is unneccessary.
Optimizing the tools dir file as per related job required to run.
Change-Id: Ia1d8a8a6dd22bec02e9f93598ddfd3d110b6c009
The new helper waits for the server to become ACTIVE again after the
reboot. This saves us a few lines of code in various tests, and is
also useful for the whitebox-tempest-plugin (see dependant patch).
Change-Id: I5c89983de0cbdae91c868fc3fefdc45b9a96fa68
Patch [1] fixes cleanup of default security group for
tempest.api.network.admin.test_negative_quotas.* tests but also
introduces a bug [2] that makes the tests fail when preprovisioned
credentials are used.
This patch reverts some changes from patch [1] and tries to
fix the cleanup of default security group in a way that works
also for preprovisioned credentials.
[1] https://review.opendev.org/c/openstack/tempest/+/797466/7
[2] https://bugs.launchpad.net/tempest/+bug/1939049
Closes-Bug: 1939049
Change-Id: I00a9cc48866e41c3c559628de5af4ba017beba39
Martin Kopec