We are stuck with juju_wait until we figure out how to deal with
all the non ['active', 'idle', 'Unit is ready.'] workload/agent
states and msgs that our mojo specs are exposed to.
This is useful for validating deployments with OVN where it is not
required to have external networking attached to every chassis.
Any chassis that does not have external networking directly
attached will forward traffic destined for the external network
through a tunnel to a chassis that does.
The SwiftImageCreateTest was running a pause/resume test for
swift proxy which does not make sense. So, break the proxy specific
tests into their own class and add a class for storage. A
subsequent change to the swift-proxy charm will be needed to add
the new proxy test class to the tests.yaml.
* Move code into test_410_heat_stack...() instead of calling functions
* Use glance and nova helper functions as available
* Simplify method for detecting duplicate encryption keys
It turns out we do need to set DNS on the overcloud subnet. It should be
the .2 of the CIDR under test and not the _admin_net's .2. There seems
there are security group rules in the way.
Make it possible for consumers of the ``auto_initialize_no_validation``
function to execute subsequent setup and test code that require vault
and the consumers of the ``certificates`` relation to be ready.
With the current order of execution, it is not possible to use the
configure function in models where ``keystone`` application is not
present.
Execute a list of functions after series upgrade if one is
supplied. This change is driven by the upgrade testing of vault.
Vault needs to be unsealed after it is rebooted.
During testing the vault credentials are stored on the lead unit.
Unfortunatly which unit is the designated leader can change during
the life of the test (particularly if the test involves rebooting
vault units). This change adds a function to search the units for
the credentials file rather than assuming its on the lead unit.
This function was previously called test_901_remove_unit, but had to
be renamed (moved to the end of the func tests); The way in which unit
removal is now performed (by running the "stop" hook) puts the the
removed unit in a "waiting" state -- which consequently causes
wait_for_cluster() (e.g. used in 910) to fail (timeout).
