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
Tempest CLI tempest-account-generator was deprecated
4 years ago.
devstack still uses the deprecated CLI for which
patch has been proposed.
As deprecation is done long time back,
'tempest-account-generator' should be now used as
'tempest account-generator'
The following commit gives the idea of deprecation
message:-
68b8b9d26f
Depends-on: I624e1dc57a3d3533322fb298c01f70241d0400ed
Signed-off by: Soniya Vyas<svyas@redhat.com>
Change-Id: I7c18998dd877d7fd065e4d1d0950b6f6413587c3
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
In python3, the response body of clients will be of type bytes,
but jsonschema.validate expects parameter of type str, so we need
change bytes to str when needed, otherwise we will get errors like
"HTTP response body is invalid (b'' is not of type 'object', 'string'"
Change-Id: If4cad1b0f706aeb5f83931cb6928806a2c5cee8e
Closes-Bug: #1864625
'test_delete_saving_image' fails because image
snapshot is produced quicker than tempest being able
to catch the 'SAVING' transition.
Hence, the testcase needs following refinement:-
1. testcase should catch the state of image in 'SAVING'
state only and then delete the image.
By this case, we can get the idea that image is
deleted in 'SAVING' state only and the testcase will
achieve its motto.
2. If the image trasits to a state other than
'SAVING', testcase can just delete the image.
Related-Bug: #1713163
Signed-off by: Soniya Vyas<svyas@redhat.com>
Change-Id: I50606c67e9f626935878aaa61d0adbc236272054
I saw in Neutron queue that default 2h timeout for this job wasn't
enough sometimes. So it's better to keep this job running a bit longer
sometimes rather than recheck everything.
Change-Id: I7c256f1ca5790cd13411d3af78ec97efcfd28b0a
spice_console and rdp_console are no longer used after
9f5adf8053196ac103302d4d7ea3b1f927caff5d, this is to deprecate
them for removal.
Change-Id: I8a882878493e3fe39bbfe0628991ee551c15d1b0
NetworkQuotaService class enables deletion of network quotas which
were neglected by tempest cleanup before.
Change-Id: I83ac30960c0be39fc5147d445cb39cb3ff4c56b2
Create_test_server in test_resize_volume_backed_server_confirm didn't
use validation_resources nor validatable=True, which resulted in an
SSHTimeout error when using fixed IP for connect_method.
When using connect_method=floating, the validation check refers
to the server created in setUp instead of this one, which prevented
this bug from being caught.
Change-Id: I778236f456ef91e78a592f99e552cb3088b1e5db
Co-authored-by: zhufl <zhu.fanglei@zte.com.cn>
Closes-Bug: #1751418
This change replaces the attach_volume cleanup call to
wait_for_volume_resource_status with wait_for_volume_attachment_remove
for multiattach volumes. This newer waiter method being able to handle
cases where multiattached volumes remain attached and thus marked as
'in-use' after being detached from another instance.
Closes-Bug: #1858841
Change-Id: I4e9d253cad1b797940c2c1f922b66602ba592416
In Ussuri, nova is hoping to implement support for extra spec
validation. If or when this is completed, only extra specs that are
recognised will be permitted by default. We're currently using a number
of arbitrary extra specs to validate the 'os-extra_specs' API meaning we
will fall afoul of this validation. Head the issue off now by using
recognized extra specs, namely 'hw:numa_nodes' and 'hw:cpu_policy',
instead.
Change-Id: I95a1050d6a5e2e40793ae7f18ff0d326455b4b36
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
Avoid creating a SSH client with a proxy client having the same
connection parameters. This will prevent from creating a SSH tunnel
within the same client.
This patch also provides aditional information in the exception
message, in case of SSH connection error, about the proxy client
configured in the SSH client.
Change-Id: I4fcffb7e26b0adc0e39dc13085f93db6495c3bd6
Related-Bug: #1860586
