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
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>
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
In test_create_server_from_volume_snapshot tearDown would trigger
bootable volume and snapshot deletion in the correct order but not
wait for the bootable volume to be deleted, causing snapshot
deletion to fail.
This change makes the scenario test explicitly delete the bootable
volume to avoid the race condition in tearDown.
Change-Id: I3fe2ce349ce629bfc96f6ddfb45b22687a1be137
Co-Authored-By: Alan Bishop <abishop@redhat.com>
Closes-Bug: 1863750
This change adds a new attachment client to allow for CRUD operations
against volume attachments as now exposed by the Cinder v3 API.
Change-Id: I0171dc0a87800ad33c176c6b6540fbc3db025709
devstack-plugin-ceph-tempest is py2 job and not
supposed to run on master gate. Moving
devstack-plugin-ceph-tempest-py3 from experimental pipeline
to check.
Change-Id: I8a15d919f9902315c4a8d27d73dabbcc5be8d8de
If live migration tests are ran on environment with multiple AZ and
destination host for live migration is chosen from different AZ then
nova scheduler would stop such migration and live migration tests
would fail so in the case of CONF.compute.compute_volume_common_az
being set in config file, choose destination host from the same
availability zone (the same happens with cinder AZ).
Change-Id: I6bfad96ae3aa6cd8efd7ae2a0ce01c53140f617a
