We have a lot of Tempest public interfaces which are used by the
tempest plugins and sometime it is not easy to know breaking changes
as we do not test all plugins test when any change merge in Tempest.
Example: https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/937725
To avoid these breaking changes at some extend, let's run the cinder
tempest plugin tests in one of the Temp[est job. Evantually, we can
add more plugins tests if needed but I think cinder-tempest-plugin
uses a good amount of interfaces.
Change-Id: I80c2b77936ac3220ff05232877eaf6fbac4743a5
eventlet>=0.37.0 drops headers with underscores on the floor; as a
result, account and container metadata may not be stored properly.
See https://github.com/eventlet/eventlet/commit/ed743d75
Change-Id: Idcaacfed5e0203760e9cb2911d93700d8cb63cb5
This change fixes an optional `encryption_id` parameter
for updating and deleting encryption types to comply
with OpenStack documentation.
`encryption_id` is optional because only one
`encryption_id` can be associated with a `volume type`,
therefore, an encryption type is deleted using
`volume type`.
`encryption_id` is only used for Cinder
notifications.
Closes-bug: #1835186
Co-Authored-By: Evan Wever <evan.wever@gmail.com>
Change-Id: Ieca29000b5754373e6250818ccf2b3b6d4ef80e2
This patch enhances the floating IP association process by allowing the
fixed IP address to be explicitly passed. This provides greater control
and ensures the correct port is targeted when associating a floating IP,
resolving ambiguity when multiple ports are present.
Change-Id: I829703a63397a1116360a768dbccdb1f237be87c
Related-Bug: #2089798
This reverts commit 9400fb6f7cc67bf129eebaf25efe129ce5bf9bbd.
Reason for revert: neutron-tempest-plugin is fixed now
Change-Id: Ibb2d7ca35165fc6ea38c278fb9faf54a4dcd4aff
With Ia1a57b4d0127baaa614191cc013115732ca1cceb change additional
creation of test VM was added. New VM is created without security
group specified. It leads to default security group usage. As there
is no allow rules for ssh access in default security group - ssh
check after VM rebuild will fail. Also additional issue was found,
that we check VM for class setup, not the one we rebuild.
Fix adds additional (dedicated) validation_resources for test VM
so VM will use custom security group in newly created validation
resource and check will be performed against this new validation
resources.
Closes-Bug: #2085533
Change-Id: I4f2b9d689e45f85ff5a767df805a673d71622d50
The memory consumption of Tempest can be high when HTTPS is used and
Tempest uses an older version of urllib3 as a dependency (1.26.x). This
is caused by Tempest, in conjunction with urllib3, loading certificates
into memory for each instance of RestClient and releasing them only at
the end of tests execution. The issue is particularly noticeable when
the certificate file is large.
This patch fixes this issue by clearing the pool in PoolManager after
each HTTP request.
Closes-Bug: #2088074
Change-Id: Iaede004522cd2e2386bac14ff725fa8e31d4991f
Tempest plugin sanity job is failing with below
error
- https://zuul.opendev.org/t/openstack/build/2c2ed82bd12948b98d9ea7e2ebe625a8
from os_ken.tests.integrated.common import quagga
ImportError: cannot import name 'quagga' from 'os_ken.tests.integrated.common'
To unblock the Tempest gate, making it non voting until plugin is fixed.
Change-Id: I2c0f3fa92b4a0ad98698b755b40614a85230756f
As per 2025.1 cycle testing runtime and community goal[1] we
need to migrate upstream CI/CD to Ubuntu Noble(24.04). Most
of the Tempest jobs will be migrate automatically once
devstack base job start running on Noble(Depends-On). As we
need to run at least one job on Ubuntu Jammy(22.04), I am
adding a new job tempest-full-ubuntu-jammy.
Few job like tempest-full-multinode-py3 and plugin sanity
job needs to override the nodeset. multinode job needs to
run on Jammy till stable/2024.2 and on Noble from master
(2025.1) onwards. Stable branch jobs testing stable branch
needs to keep running on their supported distro version.
Also bump the autopep8 to 2.1.0 as older version does not
work on python 3.12 and fail with
error: "ModuleNotFoundError: No module named 'lib2to3'".
- https://github.com/hhatto/autopep8/issues/581
To resolve the deps of autopep8 2.1.0, I need to bump
the hacking to 7.0.0 (this gives flake8 7.1.1 and
pycodestyl>2.12 which is needed by autopep8 2.1.0)
Depends-On: https://review.opendev.org/c/openstack/devstack/+/931697
Depends-On: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/932155
[1] https://governance.openstack.org/tc/goals/selected/migrate-ci-jobs-to-ubuntu-noble.html
Change-Id: If4bf5e8f8c663933d70349aa8ddb45c28e8e558b
hacking was indirectly capped by pycodestyle. This bumps hacking to
apply the rules recently added.
Also remove the note about pip's behavior, which is no longer valid
for recent versions.
notes:
- T117 test is now disabled. There are a lot of lines violating
this rule and we have to decide if we really want to enforce it.
- Once this is merged, we have to update bump hacking in some plugins
which import hacking extensions from tempest.
Change-Id: I5ee5e152418079f9f2720eb97c3a5361edba2695
This lets us wait for one of multiple target states so we can more
effectively avoid race conditions where we miss an intermediate state
and first poll the final one.
Change-Id: If12c35d38c03fa329ebbf536e2fcd3ff2bd136de
This patch removes the space in front of two lines in the help text of
the "pause_teardown" configuration option to resolve issues with modern
versions of docutils which will raise ERROR: Unexpected indentation. [docutils]
Closes-Bug: 2086747
Change-Id: Ib295ea1c6ff521d880180143a8ed40fbc73168c9
test_unified_limits scenario test the image service
limits and we should check the glance service is enable
or not. Adding it in skip_checks method which run very
first thing (before resource_setup()) to start the test.
Change-Id: I86637ae2fd4e00ce5571d7fac8ae41418637cf29
When fixed network in tempest config is used for validation, IP
address will be returned in REST response to get server api
only after VM will be in ACTIVE state. AS it mentioned in comment in
source code:
"
NOTE(danms): We create these with no waiters because we will wait
for them to be validatable (i.e. SSHABLE) below. That way some of
the server creation overlap each other and with create_port.
"
But wait_for_ssh_or_ping will call get_server_ip which fail for
server in building state (as there is no IP in server properties)
Finally we got KeyError: '<Network Name>'
Closes-Bug: 2086461
Change-Id: I21c5a81c41e771f7566bf19cac8e3b8f5f190b27
If glance refuses to allow bad images to be uploaded, then we cannot
even register them to then test against nova or other services. Gate
these tests on a knob indicating whether or not glance will allow
them to be uploaded. The ListUserImagesTest class depends entirely on
being able to upload random data as every format/container, which is
fundamentally not something we can do with glance enforcing content
rules.
This makes the tempest-slow-py3 job disable glance image format
inspection so that we can get the compute tests to run.
Depends-On: https://review.opendev.org/c/openstack/devstack/+/931026
Change-Id: I05bb233cf1482895b96396852a15532295d3829b
In the DHCPAgentSchedulersTestJSON.test_dhcp_port_status_active test
it was checked if all ports from the network are ACTIVE. This is
typically correct but in case of the e.g. ML2/OVN backend with deployed
Neutron DHCP agent (which is rare but still possible, supported and
required in some corner use cases) this test was failing as in addition
to the port with device owner ``network:dhcp`` there was also
``network:distributed`` port created by the ovn driver and this port is
DOWN which is normal.
To avoid such false failure of this test this patch adds filtering only
for the ports with the owner like: ``network:dhcp``.
Change-Id: Id53a4b4dffe5ec18bbd9eaf2a9e74175b4dd87bb
We are going to release Tempest new tag 42.0.0 to declare
the end of support for stable/2023.1. stable/2024.2 constraint
is latest stable constraints tested with current tempest hash
which is going to be used for 42.0.0 release.
Further information:
https://docs.openstack.org/tempest/latest/requirement_upper_constraint_for_tempest.html
Change-Id: I2db8c23168c494e5e84e12dd166ff6d7cd5c1223
This marks the end of support for stable/2023.1
which is moving to 'unmaintained' stage[1].
This adds the release note to mark the end of
support of 2023.1 as well as drop the job.
https: //lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/UDQAC7SR5JAQJE5WBAG54A2MTBVBTJ44/
Change-Id: Ia91d9f4590f0b595a306a15f2c776cbabee169ab
This patch adds to test_server_connectivity_live_migration
a verification of the downtime that affects the metadata service during
a live-migration.
A script is executed on the VM instance in background while the instance
is live-migrated. After live-migration is completed, the script output
shows the duration of the metadata outage and the test compares that
duration with a configured threshold.
Change-Id: Id1c58a2fec14ff268c22efc3551fa36f3480f1a0
In this cycle, oslo library are dropping the
python3.8 support. Without oslo libs, Tempest
cannot support the python 3.8. Tempest can be run
in virtual env and upstream CI also test the stable
supported branches in virtual env. If anyone want to
test the cloud on python 3.8, they can still run the
Tempest in virtual env python 3.9.
This patch removes the support of python 3.8 and its testing.
Change-Id: I3f540da045c5e89a3f09ce2cf94877c1560f3436
The cleanup method ``_remove_router_interface_with_subnet_id`` should
wait for the router interface (port) activation before trying to delete
it. That will prevent a race condition between the deletion and the
port update.
Closes-Bug: #2083287
Change-Id: Id9029eb5a0558e74c62248fa08689aa1adee961a
There is a race in Nova where an instance being shelved is set to the
SHELVED_OFFLOADED vm_state before the instance.host is cleared. It
appears to be non-trivial to fix given the comments in that code
explictly say the updates have the be in that order.
This works around the issue by waiting until the instance.host is None
before considering the shelve offload to be completed.
Related-Bug: #2045785
Change-Id: Ia45247a7aa14eb5f0038d4512a0b4ebe6af5a573