The difference in how openstack-dashboard and every other service uses
policies continues to create special cases. This set of fixes deals
with some more of those differences.
* Addition of the (incomplete) openstack-dashboard test.
* Modification of other charm policyd override tests to support
multi-file policy overrides resource ZIP.
The current implementation may miss waiting for config change to
actually happen as it in some circumstances jumps to waiting for a
idle state prior to the model executing anything.
Add a wait for agent status `executing` immediatelly after config
change to avoid this.
Fixes#123
It would be awesome if the first iteration of a ARP lookup, ICMP
echo and ICMP reply on a newly created instance was always
successful. Sadly this is not the reality.
Increase wait attempts for availability of volume created from image
in CephRBDMirrorTest. This is taking longer as of Nautilus due to
switch to using juju storage backed by undercloud cinder taking
longer than prior method of directory-backed OSD devices.
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
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.
Alex Kavanagh
Alex Kavanagh
David Ames
coreycb
Frode Nordahl
Chris MacNaughton
Liam Young
Jose Delarosa
James Page
Edin Sarajlic