Two test_network_basic_ops tests are failing consistently in
centos-8-stream jobs (nova side tempest-integrated-compute-centos-8-stream
and tempest tempest-full-py3-centos-8-stream jobs).
1. tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_hotplug_nic
2. tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops
Failure: https://zuul.opendev.org/t/openstack/build/e0db6a9a7ba04e66b0781ba7d259357d/logs
This is blocking nova and tempest gateso making the centos8 stream job
non voting until bug is fixed.
Related-Bug#1957941
Change-Id: Ia8c575b1accf4fa2a25b903bf9bf5a614752e344
There is a non-negligible number of tests in tempest that need accounts
generated by account-generator with a concurrency of at least 2. Running
these tests with accounts generated with the current default value for
concurrency makes them therefore fail.
This change sets the default value for concurrency to 2 and updates
the documentation for --concurrency parameter.
Closes-Bug: #1948935
Change-Id: Iada980beff9db3c8cd02c84d0d7602264b66ddf8
When doing the attachment of volume with glance host, the
"server_id" field of volume attachment response is null which is
not handled in the schema validation of list volume with detail.
This caused a failure in one of the tempest volume test
"test_unmanage_manage_volume" where we do a list volume with
detail request and one volume (probably from other test running
in parallel) existed with an active attachment to the glance host[2].
We can see that the "server_id" field of the attached volume is null[3].
The "server_id" field is only present when doing the attachment
with nova.
This patch allows the "server_id" to be "string" as well as "null" type
to handle both nova and glance usecase.
[1] https://86aa517b6cb393144dd6-d78b0c94e26e635eac828273888f290f.ssl.cf5.rackcdn.com/822731/1/check/glance-multistore-cinder-import/e52281e/testr_results.html
[2] Body: b'{"volumes": [{"id": "e11beb8b-e170-4c5c-945b-e854c01f85ab",
"status": "in-use",...
, "attachments":
[{"id": "e11beb8b-e170-4c5c-945b-e854c01f85ab",
"attachment_id": "5132d152-54c3-4aa6-90e8-f13d2d1d0028",
"volume_id": "e11beb8b-e170-4c5c-945b-e854c01f85ab",
"server_id": null,
"host_name": "ubuntu-focal-inmotion-iad3-0027876140",
"device": "glance_store",...
[3] "server_id": null
Closes-Bug: #1956340
Change-Id: I92d4d49bf5fe52f3417555260e0771397f18334d
Fixes intermittent tempest unittest failure of "test_fix_argument_yes".
The bug was in check_uuid.py and not in the test itself. As part of
the fix and backward compatibility, enabled check_uuid.py to run a
validation of a py module from any dir by adding --libpath parameter to
argv.
Closes-Bug:#1918316
Change-Id: If5d3a3852320e1d3b26af433f7a66be7d42e2b84
API microversion fixture is used to set the API
microversion on service client and reset it back
after test execution. That is done in setUp()
method and due to that API microversion is not
set on service client during resource_setup()
method and any API call will be requested on base
version.
To sync the complete test execution of test class
with requested API microversion, this commit moves
the API microversion setting in resource_setup()
method.
Closes-Bug: #1881863
Change-Id: Ia4b884a79cc0e50057dd57090737332bd76da37e
We have moved the API microversion fixture to
tempest.lib.common.api_microversion_fixture location.
This commit deprecates the old fixture so that we can
remove them in Z cycle.
Change-Id: If38aa21a4cd99d2a5fe4a5c3b41214cd54f97f8d
Tests should be explicit about their use of admin credentials. The
base compute admin tests class overrode self.image_client with the
admin version. Stop doing that, and introduce a new
self.admin_image_client client that tests can explicitly use.
Needed-by: https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/805300
Change-Id: I1a0c84b41b1b77d3a618a8f15448909bd12a0742
The method is deprecated since Python 3.2[1] and shows the following
DeprecationWarning.
/usr/lib/python3.9/unittest/case.py:1134: DeprecationWarning:
assertDictContainsSubset is deprecated
warnings.warn('assertDictContainsSubset is deprecated',
[1] https://docs.python.org/3/whatsnew/3.2.html#unittest
Closes-Bug: #1938103
Change-Id: I2e868d13d52a2d3c6081a8b756fbe83f8b57cf66
This reverts commit 5b91aea1c6.
Reason for revert: Investigating whether this is still an issue. There is an extremely similar test (GroupsV320Test.test_reset_group_status) that was reported to intermittently fail (Bug #1783566); it is not currently skipped and I haven't seen failures reported for that one in a long time.
Change-Id: I2d252be140bd728ea01460a61a3097c6f3a2dc82
openstacksdk-functional-devstack should be part of
integrated gate so that cross service-sdk testing
can be covered to avoid any regression.
Change-Id: Idaab1b0952b2d6d9c0e2b9b255ec401d2e315b19
tempest.api.identity.admin.v3.test_tokens.TokensV3TestJSON.test_rescope_token fails
if not used default value for CONF.identity.default_domain_id
Closes-Bug: 1951446
Change-Id: Ie08d570907ddf9102c1297f717355a7f772aabb8
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 Tempest is branchless and needs to support older
supported stable branches, let's test it with all the
python version supported in those supported stable branches.
For that, we need to explicitly dd the py jobs instead of using
the template. This way, we will explicitly know that we are testing
all supported python versions when the new release template bumps the
min python version in the template.
In Yoga testing, we are making py3.9 job to run as voting, so
adding py3.9 job as voting.
Change-Id: I422da8da06509e529f4091e21cdc3d392d3cf910
Zuul