e56fc689e1
Previously, the stop_stack message accidentally used the engine_life_check_timeout (by default, 2s). But unlike other messages sent using that timeout, stop_stack needs to synchronously kill all running threads operating on the stack. For a very large stack, this can easily take much longer than a couple of seconds. This patch increases the timeout to give a better chance of being able to start the delete. Change-Id: I4b36ed7f1025b6439aeab63d71041bb2000363a0 Closes-Bug: #1499669 |
||
|---|---|---|
| .. | ||
| common | ||
| functional | ||
| scenario | ||
| __init__.py | ||
| .gitignore | ||
| 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