tempest 30.0.0 release

meta:version: 30.0.0
meta:diff-start: -
meta:series: yoga
meta:release-type: release
meta:pypi: yes
meta:first: no
meta:release:Author: Ghanshyam Mann <gmann@ghanshyammann.com>
meta:release:Commit: Ghanshyam <gmann@ghanshyammann.com>
meta:release:Change-Id: I7e0b60e3f16de6ddde4a55c70c6ff4c11ad723c1
meta:release:Code-Review+1: Martin Kopec <mkopec@redhat.com>
meta:release:Code-Review+2: Elod Illes <elod.illes@est.tech>
meta:release:Code-Review+2: Hervé Beraud <herveberaud.pro@gmail.com>
meta:release:Workflow+1: Hervé Beraud <herveberaud.pro@gmail.com>

Change-Id: Ide70ba2077caeef8c3b30a2399861aa5261d0bdc

We are going to release Tempest new tag to declare the start of
support for stable/yoga. So that new tag use stable/yoga
constraint in the tox env.

For example: if anyone use Tempest new tag (30.0.0) in future say
1 year later then tox env also should use the yoga 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.

Change-Id: Ie3159da1b9b73652f52cf22d87ab1dd0ae6411d9

Compute microversion 2.75 made the rebuild and update server
response same as get servers
- https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#id68

Partially Implements: blueprint fix-microversion-gap

Change-Id: I1728e5de0e815def0fe31c242203bd9f36dc41f4

Compute microversion 2.45 changed the response
of create image and create backup APIs.

create image schema already covered
- https://github.com/openstack/tempest/blob/fec2c93cdcc14ad08d0a35136ee287525e7a4879/tempest/lib/api_schema/response/compute/v2_45/images.py

This patch adds the schema for create backup API.

Partially Implements: blueprint fix-microversion-gap

Change-Id: Icfeec8957c58472e7f176680d48745b5c5350b55

This adds a sequence of unified limit updates and verifications of
enforcement for servers, vcpu, ram, and disk. This is safe to run in
parallel with other tests because only project scoped limits are being
tested in this scenario.

Related to blueprint unified-limits-nova

Change-Id: I37d3896a037e2d4d1004abc52f6e93fd0025f981

centos 9 stream is testing runtime for Yoga so
let's add it in tempest gate. This job is failing
due to bug#1960346 and it will be helpful to know the
job status when we add the fixes with below series:
- https://review.opendev.org/q/topic:wait_until_sshable_pingable

Related-Bug: #1960346
Change-Id: Ib91f67fb9a592e91649e06bb2821f452b36b49f0

add image schemas for image V2

Change-Id: Ica35b854dc2f2f36b62c71025dd3f0440d93c85a

Waiting until the test instance is SSH-able before continuing
the test will help us avoid failures to detach a volume from
server, more info in the related bug.

Related-Bug: #1960346

Change-Id: Id5496572ce6cef06e71bae1a1040b274bacf4f79

Waiting until the test instance is SSH-able before continuing
the test will help us avoid failures to detach a volume from
server, more info in the related bug.

Related-Bug: #1960346
Change-Id: I5ad4aa04f02001efa06616bf77e03e018206d1fe

This change introduces two new instance state waiters and uses them to
extend the existing tempest.common.compute.create_test_server wait_until
state support.

They are being introduced in an effort to allow the guest OS time to
start *before* we start attempting to interact with it either directly
by connecting to the instance or indirectly by hot-plugging or
hot-unplugging devices. The latter on some virt backends being an issue
if the guest OS is unable to respond to the underlying ACPI requests
sent to it.

It should be noted that these new states rely on the instance already
being ACTIVE before we begin to wait for the instance to either become
pingable or accessible over SSH. This is taken into account and will
always happen for these states even if validation isn't enabled in the
environment and thus it isn't possible to wait until the instance is
pingable or accessible over ssh.

Change-Id: Ib14fa7dc5c8093eed498049cd0a56c8ac6853660

Change-Id: I4186beaf1d083a370d46cf1d3273e067887b0f73

This reverts commit d4c9cc89 which
introduced a waiter to fix a bug in Tempest. Unfortunately that broke
neutron-tempest-with-uwsgi job where some of the tests started to fail
due to timeouts - waiting for the floating ip to get attached to a server
prolonged the tests which caused the timeout (it seems the ip attachment
process takes longer on an environment with uwsgi).
The failing tests also didn't require an attached floating ip or they
did however long enough after the server creation thus it is redundant
to wait for the ip attachment at the beginning (when the resource is
created) when it can happen "in parallel".

This patch moves the waiter from the common file to the test class
where the waiter is needed to fix a bug [1].

[1] https://bugs.launchpad.net/tempest/+bug/1945495

Closes-Bug: #1960022
Change-Id: Iddfa4ef874328fdee5418de5a8b1112007541883

stable/ussuri job was made non voting due to
bug#1959467

- https://review.opendev.org/c/openstack/tempest/+/827258

As bug is fixed now, let's revert it to voting again.

Change-Id: I834300ee8d9ee8952284b55f53d97456a1ca6032

The TaggedAttachmentsTest class queries server metadata to see if the
tagging is visible from the guest. However when the check fails it does
not log what was the faulty metadata. To make troubleshooting easier
this patch adds logging for the error cases.

Change-Id: I58f6fefef0f0a9db2f7fdf2a1a0125f616319949

[1] Added random int to flavor name but that resulted into
TypeError: can only concatenate str (not "int") to str.

Concatenate using % operator to fix it.

Also make tempest-full-ussuri-py3 job non-voting temporary
to unblock gate, can be reverted once [2] is fixed.

[1] https://review.opendev.org/c/openstack/tempest/+/826946
[2] https://launchpad.net/bugs/1959600

Related-Bug: #1959467
Change-Id: I76e15b6b52bb44fec550ead510186c644c4a1c7f

In a couple of the tests a new flavor is created by appending the
string 'extra' to the existing flavor name. The existing flavor name is
however CONF.compute.flavor_ref, which isn't unique. If two tests that
create the flavor run at the same time, there will be a 409 collision
and one test will fail.

This appends a random int to the new flavor name to prevent conflicts.

Closes-Bug: #1959467

Change-Id: I9928e2be9c749f69eea9a9d4f9e8fe03ef4ef612

This adds a config option to indicate the presence of the unified
limits feature in the compute service and skips tests that depend
on the feature being present or absent.

Related to blueprint unified-limits-nova

Change-Id: I9508b41f1a0a208dbce090a4143cb87b858fc5f2

The test could fail on an adresses mismatch when the test server
didn't have floating ip assigned yet at the beginning of the test.

Closes-Bug: #1945495
Change-Id: Ic99ba61d87dfc24a684263d41e0caa4f54d1d263