'Member' role has been deprecated and replaced by 'member'.
The patch replaces the leftover occurrences of 'Member' by 'member'.
Change-Id: I857655b8568eb2df1bb9bc263117119388d42f01
Closes-Bug: #1330132
In delete_group() method the group is deleted first and
then the volume information is fetched which internally
trys to find all the related groups. As group delete request
was placed earlier than volume list and the group might be
deleted before volume list try to find the group
information, it returns 404.
This is race condition based on group is finish its deletion
before list volume requests or not.
Better is to fetch the information of volumes first and then
delete the group. And use that volume info later
to cleanup the volume also if requested.
Change-Id: I5b52ebac2f325bfeda51773c90cb40e7f7e02c67
Closes-Bug: #1882116
The test_create_second_image_when_first_image_is_being_saved
introduces race and might if the first image was created quickly.
Blacklisting this for now untli we decide what to do with this next.
Change-Id: I15df606fd163c75bf265d406771e4e946a1d38b9
Closes-Bug: #1881592
Closes-bug: 1879359
https://bugs.launchpad.net/tempest/+bug/1879359
Sorts the roles in the scoped tokens so that the
test case does not fail
Change-Id: Iac94eab78035a9b0f3926bd7da237ae4f5fb68d8
Add image "version" metadata to the snapshot image in
test_snapshot_pattern as shown in the related bug. Creating
another test just to update the metadata is not worth it.
Change-Id: I2f1093616dc7c4268a0bda5a4854da23423f4cab
Related-Bug: #1717547
This is to add response schema validation for volume snapshots.
Change-Id: I7de5569ed58fb6a3bf8115f89163cd951c19d951
partially-implements: blueprint volume-response-schema-validation
This is to add response schema validation for volume pools.
Besides, free_capacity and total_capacity in "List all back-end
storage pools" should be free_capacity_gb and total_capacity_gb,
Ic0690d12147fa63b903f3442eccde88c1d501711 will fix them.
Change-Id: I8ae2cd178b91756bb488c02a1a2fcdf64f572155
partially-implements: blueprint volume-response-schema-validation
This is to add response schema validation for volume group
types.
Change-Id: I81c6cfd854507cdd295c1356370d73c1a4f0712c
partially-implements: blueprint volume-response-schema-validation
This is to add response schema validation for encryption types.
Change-Id: Ic8e1dddd4a7e7bc57cc2959f1a7991dd4be22194
partially-implements: blueprint volume-response-schema-validation
Switch to openstackdocstheme 2.2.0 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* parallelizing building of documents
Update Sphinx version as well.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
Set openstackdocs_pdf_link to link to PDF file.
Depends-On: https://review.opendev.org/728938
Change-Id: Ia31f69f00eb24771bf700b4e25ae73a09c1c8aed
Now that we no longer support py27, we can use the standard library
unittest.mock module instead of the third party mock lib.
Change-Id: If1de2f48da1fd6ed3f96c98b8dce9eace4f8095d
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
The initial set of tests would incorrectly attempt to use a volume based
snapshot image as the rescue image. Such images contain no actual image
data and are just used to store metadata such as the
block_device_mapping that is in turn used when creating new instances
from the backing volume snapshots.
This wasn't initially noticed as the tests pass on the default file
based imagebackend in Nova that allows zero length sparse files to be
created. This failed however when the rbd imagebackend was used as the
import process into rbd does not accept zero sized files to be used.
To correct this an image based instance is now always created and used
to generate a suitable rescue image with each test. An additional
instance is then also created for the boot from volume based tests to
ensure the correct mapping is used.
The boot from volume snapshot test is also removed and the remaining
boot from volume tests are marked as slow given the additional overhead
of creating a second instance using these tests.
Change-Id: I7356b54bef0c614d9bfd1ed0d7b42574b58966f9
Closes-Bug: #1876330
This avoid neutron error that IP address x.x.x.x already
allocated in subnet as the public network from tempest.conf
is shared amongs multiple test cases which may ask for ip
address in parallel to this test case execution and might end
up in race condition.
Note:Interop/Any other user doesn't use this test location
so we should be good to move the location
Change-Id: Ibf5ad52062b3719899a123a799f5f4f8e961f609
Closes-bug: #1676207
Logs: https://bugs.launchpad.net/tempest/+bug/1676207/comments/13
Microversion 2.59 [1] compute API added a "uuid" parameter to the body of
the following migration responses:
- GET /os-migrations
- GET /servers/{server_id}/migrations/{migration_id}
- GET /servers/{server_id}/migrations
This commit adds the uuid to the response validation schema for
list_migrations.
[1] https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#id55
Change-Id: Ic748f70d90446c79324df30147e4a270b72d710e
floating_ip variable contains an old state of the floating ip - the state
which was correct before calling refresh method. In order to have the
latest floating ip data after calling refresh, the patch creates a class
as a wrapper around the refreshing ip's state and logging it.
Closes-Bug: 1788416
Change-Id: I83ca08ef77c243762210837bad800ce0c4d09fb5
hacking 3.0.1 fix the pinning of flake8 to avoid bringing in a new
version with new checks.
bumping the min version for hacking so that any older hacking versions
which auto adopt the new checks are not used.
The 2.6.0 version introduces some checks that cause failures
with the current code. hacking and flake8 cap could have solve
the pycodestyle compatible version but flake8-import-order which
does not cap the pycodestyle pulled its latest version and break
things.
Change-Id: I8996fec39e9b7c411b2708eb8baeb50aa2c28d42
test_server_rescue.py contains hard-coded volume_size value without
any option to override it. The tests should use CONF.volume.volume_size.
Closes-Bug: 1877259
Change-Id: Id502dfa06547023229ae2e6f9426eeb99da7dd89
* add additional handler so that INFO messages are printed to stdout
besided tempest.log
* replace print commands by LOG.info calls
* when --debug argument used print DEBUG messages to stdout
* add additional debug messages to improve transparency of the cleanup
execution
* use --debug argument within tempest-cleanup ansible role to see more
details directly in the output
Change-Id: Iee72dc411fdf5cda8a8eed8dd7f349e0866648ab
