0f9fc9c49b
If a unit is rebooted while executing a hook Juju will mark it as errored when it comes back. To work around this in tests, units in an error state are resolved on reboot. However, this could mask a genuine error. So, to minimise the risk only resolve units that went into an error state when running update-status as the system was in a stable state prior to reboot so that should have been the only hook running. Charm going into an error state on reboot applies equally to subordinates so use the same logic for hacluster. block_until_all_units_idle can return when a subordinate hook is still queued so check for update-status errors when manually queuing update-status run via action.
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.openstack.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