b829fae6320c5798990f7d8bbd829d22839a6234
I recently added an option to have zaza delete and relaunch a guest if it failed to be provisioned or failed a connectivity test. However, in the code to remove the an instance I accidentaly called the method that checks that a resource has gone and not the method that actually does the removal. This patch fixes that. NOTE: Only the Trilio tests use this retryer function atm
Zaza OpenStack Tests
This is a test library designed to be shared between the OpenStack Charms to improve code-reuse among the various components.
Usage
This example is taken from the pacemaker-remote charm's tests.yaml:
charm_name: pacemaker-remote
tests:
- zaza.openstack.charm_tests.pacemaker_remote.tests.PacemakerRemoteTest
configure:
- zaza.charm_tests.noop.setup.basic_setup
gate_bundles:
- basic
smoke_bundles:
- basic
test-requirements.txt:
git+https://github.com/openstack-charmers/zaza.git#egg=zaza
git+https://github.com/openstack-charmers/zaza-openstack-tests.git#egg=zaza.openstack
Description
Languages
Python
99.6%
Jinja
0.4%