WHile releasing the new tag for Tempest, we modified the
constraint in tox to be used of stable/ussuri
- https://review.opendev.org/#/c/720578/
Now new tag is released and we can bring back the master
constraint in tox.ini so that Tempest master us master constraint.
Change-Id: Ie17d4830cac1902371123c8acb4d3106ba2fd300
We are going to releease Tempest new tag to declare the start of
support for stable/ussuri. So that new tag use stable/ussuri
constraint in the tox env.
For example: if anyone use Tempest 24.0.0 in future say 1 year later then
tox env also should use the ussuri 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.
- I4268049ff91e5527e4b95fd8a70fa53ba27d56ed
Change-Id: I39e3e23a85a9abc1eda6848a6f4af77540cb81b6
Currently we rely on [service_available]ironic which
1) will give incorrect results in a mixed environment
2) doesn't work in grenade jobs
This change only allows ports to be DOWN when they have VNIC type
of baremetal.
Change-Id: If24913b7097c5252a214bb780fc786aa0c3f983b
When Tempest is used in customer site, often we are required to
provide a testcase list including testcase names and descriptions.
Now no this kind of doc is available, however, we can extract info
from tempest code to create one, but, some testcases don't have
descriptions about what the testcases are testing, so, we can add
descrption for each testcase.
There are hundreds of testcases missing descriptions, so we can
add them gradually, and limit the modified files in one patch
for the convenience of reviewing.
Change-Id: Id90d6fedccc84aa9548fba62b5926a75050ab443
partially-implements: blueprint testcase-description
This commit adds x/glare and x/tap-as-a-service to the BLACKLIST to
avoid sanity-job failures like following.
Failed Plugins: x/glare, x/tap-as-a-service,
+ [[ -n x/glare, x/tap-as-a-service, ]]
+ exit 1
It looks the root cause is related to pg_config installation but not
sure. So, this commit just blacklists them as a workaround.
Error: pg_config executable not found.
Change-Id: I03c6f01593b8e414b5e111d0e0c971ae156da715
With the introduction of expiring group memberships, there is a
new attribute `membership_expires_at` when listing user groups.
This patch updates the test to check the attribute and then
ignore it for group dict comparison.
Change-Id: I4294a879071dde07e5eb1da4df133de8032e1059
Partial-Bug: 1809116
The introduction of Icd7fcb87a09c35a13e4e14235feb30a289d22778 blocks
attempting to update or swap a volume that is currently attached to
multiple instances. This change adds a simple test to assert that a
BadRequest is raised when this is attempted directly against the compute
API.
Future work will also cover this failure when part of a wider volume
retype or migration flow.
Change-Id: I931a810901cf7847a8259e44a30b0150aad859f2
Previously, create_test_server() in the base compute test class did
not provide a way to create a server with admin privileges. This can
be necessary when using APIs that are admin-only by default, for
example the `host` parameter when creating a server in Nova
microversion 2.74. This patch adds a clients kwarg to
create_test_server(). This kwarg is then passed to compute.common's
create_test_server() instead of the cls.os_primary clients that was
harcoded previously.
Change-Id: Ic47e6a4ced54739de9325bb14e332ba15cdb210f
The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.
Fix problems found.
Update local hacking checks for new flake8, remove vi check, it's now in
hacking as H106.
The tempest plugin is used on older branches as well.
We really only need hacking on this repo anyways,
where we no longer support python 2, so here we
make the requirement specific to python 3.
Change-Id: I3f4216f66606fbc450a46c93de306399b7f3cd65
Let's check no specific group present instead of list is empty
in test_group_snapshot_create_show_list_delete.
This maybe a reason of failed test due to some inconsistency.
Closes-Bug: #1869852
Change-Id: I41884567ae07b4d6a28667d2a3a792b63e1a6cfa
x/kingbird doens't seem to be compatible with tempest anymore
which is breaking our tempest-tox-plugin-sanity-check gate job.
Change-Id: Icdaff49bbc2ba0e59cd528d55cad6c35014b7ad0
Currently race condition can occure in
tempest.api.compute.servers.test_attach_interfaces.
AttachInterfacesUnderV243Test.test_add_remove_fixed_ip
when floating IP added during resource preparation doesn't appear in
the list of original IPs that is created at the beggining of the test,
which then confuses the test
and floating ip is later recognized as fixed IP added in the test.
more details including log:
https://bugzilla.redhat.com/show_bug.cgi?id=1752416
This change ensures possible floating IP added during server
creation is always present in the set of original IPs and also
during every comparasion of IPs.
Closes-Bug: #1866179
Change-Id: Ic3a3e0708714b6d6c9c226e641e1c520e5ebde9d
Signed-off-by: David Sedlák <dsedlak@redhat.com>
Network quotas could be deleted after deletion of project. This
caused the cleanup to fail as network quotas have to be deleted
before the deletion of project.
This fix makes sure that network quotas are deleted before the
deletion of project.
Change-Id: I8576e2c6f1ae6dc90850dd3d8eade7c10942e413
add unittest for create and list resource types association
interface of metadata in glance module
Change-Id: I3f7bff1fcad32450b71f4ddd16e579cd53961fe9
When tested network contained more than one subnet then test failed
due to assert call.
Subnet_id option specifies which subnet should be used for testing
when more than one subnet in network is present. If subnet_id is
specified then each created VM is assigned a floating IP within
the range of the subnet.
Closes-Bug: 1856671
Change-Id: Ie4d44b16595055201e12f10982fc78683a12d41a
tempest-multinode-full is python2 version
of mutlinode testing for stable branches and
supposed to run on python 2 but it was left during
- I75868d5c9b6630fe78958ff89e58a0aced09a6b3
Change-Id: Ibec72b578424cb278006ac810bdd0359ec23de3f
Images weren't deleted properly due to bad request sent to
glance API. Also ImageService ignored 'next' parameter returned from
glance API when listing images which is required when more images
are present.
The fix lists all images properly. If 'next' parameter is present
in the glance API response then the API is asked to send next part
of image list.
Closes-Bug: 1866988
Change-Id: I9ebeccb545576e43ef0fc96c29169ae16f261f34