3aeaefc29f
If you attempt to update a stack containing OS::Heat::SoftwareDeployments resources, so it uses the new non-deprecated OS::Heat::SoftwareDeploymentGroup type instead, it deletes the group, and all of the deployments. This means that any deployment "actions" property will be misinterpreted, e.g if you have actions: CREATE, all the deployments will re-run on the update, even though it's an update, not a create. This issue exists on all deprecated resoruces, when we trying to upgrade to new version of it by update. This patch fix above update issue by check if resoruce was deprecated and been update by replacing resource (which is the parent class of existing resource). Change-Id: Ib7880120a90c4497a7ceea53eee55c220a28d14e Closes-Bug: #1528958 |
||
---|---|---|
.. | ||
common | ||
functional | ||
scenario | ||
.gitignore | ||
README.rst | ||
__init__.py | ||
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