tempest 29.0.0 release

meta:version: 29.0.0
meta:diff-start: -
meta:series: xena
meta:release-type: release
meta:pypi: yes
meta:first: no
meta:release:Author: Martin Kopec <mkopec@redhat.com>
meta:release:Commit: Ghanshyam <gmann@ghanshyammann.com>
meta:release:Change-Id: I92e56613d3d126e0a5c32eadb3e35d47635c304c
meta:release:Code-Review+1: Martin Kopec <mkopec@redhat.com>
meta:release:Code-Review+2: Thierry Carrez <thierry@openstack.org>
meta:release:Code-Review+2: Hervé Beraud <herveberaud.pro@gmail.com>
meta:release:Workflow+1: Hervé Beraud <herveberaud.pro@gmail.com>

This commit adds the releasenote to tag Tempest for Xena release.

Change-Id: I9a93701928221e2aec6eb69847b11f77c720028e

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

Below plugins are failing with error:

File "/home/zuul/src/opendev.org/openstack/tempest/.venv/lib/python3.8/site-packages/psycopg2/__init__.py", line 51, in <module>
2021-09-08 01:14:10.471582 | ubuntu-focal |     from psycopg2._psycopg import (                     # noqa
2021-09-08 01:14:10.471614 | ubuntu-focal | ImportError: libpq.so.5: cannot open shared object file: No such file or directory

https://zuul.opendev.org/t/openstack/build/b61a48196dfa476d83645aea4853e544/log/job-output.txt#271722

Failed Plugins: x/networking-l2gw-tempest-plugin,
x/novajoin-tempest-plugin, x/ranger-tempest-plugin,
x/tap-as-a-service-tempest-plugin, x/trio2o,

Change-Id: I485b180353c071a4b72865c87ecfd5ddd0119a9d

tempest 28.1.0 release

meta:version: 28.1.0
meta:diff-start: -
meta:series: xena
meta:release-type: release
meta:pypi: yes
meta:first: no
meta:release:Author: Slawek Kaplonski <skaplons@redhat.com>
meta:release:Commit: Slawek Kaplonski <skaplons@redhat.com>
meta:release:Change-Id: Ide030c22cf54573955e4ec8b2b98194c33238cda
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>

Test creating volume type with a repeated name will fail

Change-Id: Icfdad5c4c08e18771bf8ed5e8d3af37c3fb1f370

Fix for: https://bugs.launchpad.net/neutron/+bug/1942448

Change-Id: I1e798badceb7fbda499bfeb34c98dea0e73c24bf

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

Update volume type extra specs for non existent volume type
should fail
Change-Id: Ib36b517cab1b13d2ed4ae5bae0123bea54e4d27d

Change-Id: Ib0135cd639ea749150aba8e591b3f8de63744639

"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

Test create volume type encryption with nonexistent type id will fail

Change-Id: Iff8afc9f97133ca031d53ff6ec1fddb9ff0e899f

tempest 28.0.0 release

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

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

Tempest sanity job is 100% failing on x/vmware-nsx-tempest-plugin.
Adding this plugin until it is fixed.

- https://zuul.opendev.org/t/openstack/build/45f6c8d3c62d4387a70b7b471ec687c8
- https://zuul.opendev.org/t/openstack/builds?job_name=tempest-tox-plugin-sanity-check

Change-Id: I9c23582e5930156db21b609bc9031ee47e9d6326

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

Merge "Fixes test_user_update_own_password test cleanup problem (New password cannnot be identical to a previous password)"

The test was randomly failing which could be caused by a race
condition - the temporary files which are created during the
test weren't closed properly which could result in a situation
when they are not yet created but the test is trying to load
them.

Closes-Bug: #1918316
Change-Id: I7a5bf8b1404dbf96955b2eb96fb1a5552760a114

*vmware-nsx-tempest-plugin,networking-l2gw-tempest-plugin
 x/tap-as-a-service are removed from the list

*Updating comments for required projects

Change-Id: I8bec628a07a4e555a95d542c87fa76f6c464f1d9

This patch creates the network v2.0 loggable-resource client.

https://docs.openstack.org/api-ref/network/v2/index.html#list-loggable-resources
Signed-off by: Soniya Vyas<svyas@redhat.com>

Change-Id: I37b9397834fbb7f4ebf540dc5f8aece356ddf749