d0309937b3
When an update fails, we may have copy some chunk of resources or
parameters to the new template. If the version was updated and the new
resources require the version, this can lead to a state where the stack
is in an usable state. This synchronizes the version when a failure
happens.
Change-Id: I2faf8f3541fc800ea61c417e5575f4a56a83665b
Closes-Bug: #1620696
(cherry picked from commit
|
||
---|---|---|
.. | ||
api | ||
common | ||
functional | ||
scenario | ||
.gitignore | ||
README.rst | ||
__init__.py | ||
cleanup_test_env.sh | ||
install-requirements | ||
plugin.py | ||
post_test_hook.sh | ||
pre_test_hook.sh | ||
prepare_test_env.sh | ||
prepare_test_network.sh |
README.rst
Heat integration tests
These tests can be run as a tempest plugin against any heat-enabled OpenStack cloud, however defaults match running against a recent DevStack.
To run the tests against DevStack, do the following:
# Define DEST
export DEST=/opt/stack
# create test resources and write tempest config
$DEST/heat/heat_integrationtests/prepare_test_env.sh $DEST/heat/heat_integrationtests/prepare_test_network.sh
# run tempest selecting only these tests
cd $DEST/tempest tempest run --regex heat_integrationtests
If custom configuration is required, edit the [heat_plugin] section of
$DEST/tempest/etc/tempest.conf