66d95d65d7
A couple of changes here: * Ensure that the post-upgrade-hook runs BEFORE the config-changed to set the openstack-origin/source back to distro. The former behaviour breaks keystone quite badly. * Ensure that the charm name is used, as discovered from the model, for rabbitmq-server and percona-cluster to cope with different names for the application in the model vs the charm name from the charm-store. * Check whether the machine needs to be rebooted after the dist-upgrade (before the do-release-upgrade), and reboot the machine first. Otherwise, do-release-upgrade will fail.
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