OpenStack Testing (Tempest) of an existing cloud
370bea472b
Currently, the create_server_snapshot and test_image_defined_boot_from_volume methods assume that the server being snapshotted will have only one block device mapping. However, if the server has an ephemeral disk and/or a swap disk, it will have multiple block device mappings. This can cause erroneous scenario test failures if the first block device mapping in the image service response is not the root disk. This adjusts create_server_snapshot and test_image_defined_boot_from_volume to check for a non-null snapshot_id before using it. Change-Id: I2417d5a91ae5fbb2101b64a07b6b8c74199e8fb5 |
||
---|---|---|
doc | ||
etc | ||
playbooks | ||
releasenotes | ||
roles | ||
tempest | ||
tools | ||
zuul.d | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.stestr.conf | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
README.rst | ||
requirements.txt | ||
REVIEWING.rst | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
Team and repository tags
Tempest - The OpenStack Integration Test Suite
This is a set of integration tests to be run against a live OpenStack cluster. Tempest has batteries of tests for OpenStack API validation, scenarios, and other specific tests useful in validating an OpenStack deployment.
- Documentation: https://docs.openstack.org/tempest/latest/
- Features: https://specs.openstack.org/openstack/qa-specs/#tempest
- Bugs: https://bugs.launchpad.net/tempest/
- Release Notes: https://docs.openstack.org/releasenotes/tempest
Get in touch via email. Use [tempest] in your subject.