25ba5b654a
The purpose of this test is to ensure we can rollback an in-progress
Server resource with attached ports. However, by cancelling immediately
we create a race whereby the stack may be rolled back before we have
even started updating the stack, in which case we are not testing the
behaviour we actually care about. Inserting a delay gives Heat enough
time to process the Port and start updating the Server before we cancel
the update.
In some circumstances this could also trigger a race within Heat,
whereby the rollback traversal would not block, but the update traversal
would retrigger it anyway. This resulted in the stack rollback being
marked COMPLETE multiple times, which could also lead to errors in
deleting the old raw_template after it had already been removed. The
latter have been fixed by separate patches. The race itself should be
addressed separately.
Change-Id: I3f9db686c31659437ff4797555e6608986946572
Task: 37199
(cherry picked from commit
|
||
---|---|---|
.. | ||
common | ||
functional | ||
locale | ||
README.rst | ||
__init__.py | ||
cleanup_test_env.sh | ||
config-generator.conf | ||
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 against any heat-enabled OpenStack cloud, however defaults match running against a recent DevStack.
To run the tests against DevStack, do the following:
export DEST=/opt/stack
# create test resources and write config
$DEST/heat/heat_integrationtests/prepare_test_env.sh
$DEST/heat/heat_integrationtests/prepare_test_network.sh
# run the heat integration tests
cd $DEST/heat
stestr --test-path=heat_integrationtests run
If the Heat Tempest Plugin is also installed, the tests from that will be run as well.
If custom configuration is required, add it in the file
heat_integrationtests/heat_integrationtests.conf
. A sample
configuration is available in
heat_integrationtests/heat_integrationtests.conf.sample