test_volume_from_snapshot has extra_size hardcoded to 1 and it expects
the returned size increased by 1GB. This does not work with PowerFlex
cinder driver because PowerFlex/VxFlex OS requires volumes to be sized
in multiples of 8GB. Even if 1GB is given, 8GB will be actually used
when powerflex_round_volume_capacity = True.
Closes-Bug: #1949927
Change-Id: I04c3d6145fbc201355d38a7a058a37791227f733
Full support for CentOS8Stream in devstack didn't land until
I39ccefbd06f46adf5077f8d8001f37d3b190f040 fixed is_fedora to include the
newly introduced name.
As such the recently introduced
tempest-integrated-compute-centos-8-stream job within tempest that forms
part of the integrated-gate-compute template needs to be restricted to
branches >= stable/wallaby.
Closes-Bug: 1950296
Change-Id: I802c0cdb3c8875e33819aed335877f1caef39fef
The commit replaces DefCore committee (a former name) by
Interop Working Group (the current name) and updates a few
more old interop references.
Change-Id: I8bd05246e42c0e98a9825a4621ac9c3ed714d1dc
Nova list the interfaces attached to a server based on list of ports
bound to the server. However during detach interface nova unbounds the
port first and then deallocates the resources used by that port in
placement. The current detach waiter only waits until the interface
disappears from the interface list. This can cause that waiter returns
before the resource allocation is removed from placement cause a race in
the test asserting such allocation.
So this patch changes the waiter to wait for the successful detach
os-instance-action event for the server as that is only recorded after
the port is fully deallocated.
blueprint: qos-minimum-guaranteed-packet-rate
Change-Id: I8740f8e0cc18ffea31a9a068bccee50bf4e6fe28
I need to use os-instance-actions API in a waiter that is called from
multiple microversion tests in a later patch. So this patch adds the
microversion schemas for this API.
blueprint: qos-minimum-guaranteed-packet-rate
Change-Id: I010fbb4236ccaedb3de663e32eb22f89931d53c7
As a preparation to test Network QoS minimum bandwidth and minimum
packet rate rules together this patch the necessary packet rate API
client to tempest lib.
blueprint: qos-minimum-guaranteed-packet-rate
Change-Id: I1c5c82e8178462652c36533093958c82b5130a55
As set out in the governance repo for Xena CentOS 8 stream with py36 is
a supported platform and runtime for the release:
https://governance.openstack.org/tc/reference/runtimes/xena.html
As a result the Nova team want to run CentOS 8 stream based jobs within
the integrated-gate-compute template.
An additional tempest-full-py3-centos-8-stream job is added to Tempest's
check and gate queues to ensure coverage here.
Both jobs are given additional swap to workaround bug #1949606, a
behaviour change in QEMU >= 5.0.0 when using [libvirt]virt_type=qemu
that causes additional memory to be consumed by each running instance.
This workaround of additional swap will be removed in the future once
Nova is able to workaround this itself through a new libvirt domain
configurable.
Change-Id: I4b074dca58960b2622dde15ad7d9a91b3ba0c096
As a preparation to test QoS minimum bandwidth and minimum packet rate
together this patch refactors the existing MinBwAllocationPlacementTest
test class to allow generalization.
blueprint: qos-minimum-guaranteed-packet-rate
Change-Id: Ie589e114d08cc8bb5a524d6b242f1b29fda43983
Let's only use admin client for the operations that are really
needing it.
blueprint: qos-minimum-guaranteed-packet-rate
Change-Id: I4cc9eb76a1318c17a55d8d10d21290eac4690548
The port-resource-request-groups neutron API extension proposed in
I99a49b107b1872ddf83d1d8497a26a8d728feb07 changes the format of the
port.binding:profile.allocation value. The existing tests are depending
on the format so they are adapted now to accept both format.
blueprint: qos-minimum-guaranteed-packet-rate
Change-Id: I7c5ecfe1015dba4ad0b70bbdcacc079503c50e65
- Bandwidth Limit Quality of Service rule was added
recently (test_qos_limit_bandwidth_rules_client.py).
- There were some places that the references to the
newly added QosLimitBandwidthRulesClient was missing.
So the following changes were done:
- Added QosLimitBandwidthRulesClient reference that was
missing in clients.py.
- Imported QosLimitBandwidthRulesClient from the newly added
tempest.lib.services.network.qos_limit_bandwidth_rules_client
to __init.py.
- Added QosLimitBandwidthRulesClient reference that was
missing from __init__.py.
Change-Id: Ib0e4b3864aa42455fa52ce098961e11a2ec8d4cb
This patchset use the lib.common.api_microversion_fixture to set
the volume and compute microversions in volume API testing.
Change-Id: I99fd8589a587fea7ccf3066d6f22a4ae3afd74f5
In bug 1923194, a floating IP is associated to a server. Upon
performing the operation, Neutron sends Nova a network-vif-changed
external event, causing Nova to update its network info cache. Until
Nova does this, the new floating IP is not reflected in `server show`.
Tempest's `server show` is racing with this process, causing
intermittent failures when the new floating IP does not show up in
`server show` in time.
This patch adds a new waiter that waits for a floating IP to either
appear to disappear in the `server show` output, and modifies two
tests to use the new helper.
Closes bug: 1923194
Change-Id: I0f7e1c9096dc1903903fb31c5e854f07800efbfd
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
Use common method to delete objects and containers after Swift
testing. The used method ensures proper deletion before continuing;
simply listing and deleting sometimes raises exeptions due to delayed
executions.
Also fixes a docstring to reflect current behaviour.
Change-Id: Ieaaba496028de741f3e506dac800b151aa833333
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
Zuul