f55f69e12e
The xml.volumes_client check to translate the bootable setting on a volume object only checks for Upper case strings and bools. It turns out that this test was introduced after a bug was introduced to cinder.api which inadvertently changed the type used to set this member field. We now have a patch to fix this and put it back to "true/false" (lc strings) but since the change there's a tempest test that verifies this. This patch will check for string true/false either lc or uc, and will keep the bool check in place as well (otherwise everything will fail). This test did such a great job we should consider removing the other options for true/false representations which would've caught the original error introduced in Cinder (reference cinder lp# 1227837. Fixes bug: 1227858 Change-Id: I8a4b1f4ce3a6a420e8152ea8c66a9b3fc127fe96
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.
Quickstart
To run Tempest, you first need to create a configuration file that will tell Tempest where to find the various OpenStack services and other testing behavior switches.
The easiest way to create a configuration file is to copy the sample
one in the etc/ directory :
$> cd $TEMPEST_ROOT_DIR
$> cp etc/tempest.conf.sample etc/tempest.confAfter that, open up the etc/tempest.conf file and edit
the configuration variables to match valid data in your environment.
This includes your Keystone endpoint, a valid user and credentials, and
reference data to be used in testing.
Note
If you have a running devstack environment, tempest will be
automatically configured and placed in /opt/stack/tempest.
It will have a configuration file already set up to work with your
devstack installation.
Tempest is not tied to any single test runner, but testr is the most
commonly used tool. After setting up your configuration file, you can
execute the set of Tempest tests by using testr :
$> testr run --parallel tempestTo run one single test :
$> testr run --parallel tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_rebuild_nonexistent_serverAlternatively, you can use the run_tests.sh script which will create a venv and run the tests or use tox to do the same.
Configuration
Detailed configuration of tempest is beyond the scope of this document. The etc/tempest.conf.sample attempts to be a self documenting version of the configuration.
The most important pieces that are needed are the user ids, openstack endpoints, and basic flavors and images needed to run tests.
Common Issues
Tempest was originally designed to primarily run against a full OpenStack deployment. Due to that focus, some issues may occur when running Tempest against devstack.
Running Tempest, especially in parallel, against a devstack instance may cause requests to be rate limited, which will cause unexpected failures. Given the number of requests Tempest can make against a cluster, rate limiting should be disabled for all test accounts.
Additionally, devstack only provides a single image which Nova can use. For the moment, the best solution is to provide the same image uuid for both image_ref and image_ref_alt. Tempest will skip tests as needed if it detects that both images are the same.