The Zaza MAAS code selects interfaces that are attached to the
provided CIDR, set up as unconfigured and has link.
In the event a machine has multiple unconfigured interfaces
attached to the same physical network, adding them all to the
configuration might lead to undesired side effects such as network
loops.
We're more likely to time out while waiting for the
action's result if we launch an action while the
model is still executing. Thus it's safer to wait
for the model to settle between actions.
* Check blocked ovn-chassis units with bad config
LP bug#1919481 [0] needs to have a func-test to check if units can
handle bad bridge-interface-mappings configuration and set units
workload to block state and return to active state with good config.
[0] https://bugs.launchpad.net/charm-ovn-chassis/+bug/1919481
* Changing test_wrong_bridge_config to use config_change
Instead of using block_until_unit_wl_status, change the test_config
to be able to check blocked state for ovn-chassis units
Co-authored-by: Aurelien Lourot <aurelien.lourot@canonical.com>
distro-info hasn't been maintained for 8 years and pip is
now failing to fetch it on Python 3.8.
This dependency seems to have been introduced by accident
in 22e7ffc.
After zaza#451 Zaza's application readiness detection
has been improved, which now exposes issues from the
past that were hidden. In other words, we were relying
on a bug on Zaza's side and need to get this straight.
In this change, a charm test that subclasses the ManilaBaseTest
class can also opt-in to re-validating a share after restarting
the share services by overriding the _restart_share_instance
method.
When running Trilio tests in a scenario test there is no 'charm_name'
so the application name needs to be explicitly set when calling
the setup class otherwise some config, such as lead_unit, is
missing.
Starting with OpenStack Wallaby the LBAASv2 API will require
authentication with system scoped token unless the user has
the 'load-balancer_admin' role.
Grant role on test setup, and remove it again on clean-up.
Starting with OpenStack Wallaby the LBAASv2 API will require
authentication with system scoped token unless the user has
the 'load-balancer_admin' role.
Grant role on test setup, and remove it again on clean-up.
When Vault is running in a LXD container, test_vault_reload is expected
to fail because mlock cannot be enabled in LXD containers. Skip it when
running in containers is detected. It's useful for local development
environments with Juju's localhost/LXD provider. The test won't be
skipped in the OpenStack Charm CI since the Vault units will be run in
KVM, not in LXD containers.
Vault's runs its tests twice. In some circumstances the removal of the
vault key from the test_config dictionary can throw a KeyError. Do not
fail when this happens.
