3fb8722012
The Stack._find_filtered_resources() method returns Resource objects for all resources associated with the Stack, regardless of whether they are current (present in the template; latest version in the case of convergence). To do this, it previously created a new Resource object for every resource found in the database. However, for those resources which *are* current this is unnecessary. We can access the Resource object simply through self.resources. It turns out this is necessary for obtaining the required_by list for legacy stacks, because only the Resources obtained from self.resources also appear in the Dependencies graph obtained from self.dependencies. The required_by list is read when listing or showing resources, which would either return an empty list or fail for legacy stacks. This patch also makes the Resource.required_by() method more robust in its error handling. Change-Id: Id438336e5c88dc7c2d168ba01ee703faa17e8b8e Closes-Bug: #1703703 Related-Bug: #1523748 (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