Add test for the new nova_cc charm action syncing AZs
The new action is meant to sync the availability zones from the
underlying Juju provider with the OpenStack availability zones.
It is useful within MAAS environments to map the MAAZ AZs to
OpenStack AZs.
Also fix output check logic for sync az test.
The validation logic for the sync az test checks the specific output of
the command text, but this is dependent on ordering. The code also
validates that the hypervisors are added to the appropriate host
aggregates, so this changes the test to verify the action was successful
and has some output.
Also use the availability-zone based on the configured settings.
In the attempt to sync the az test, the availability zone is assumed
to be the JUJU_AVAILABILITY_ZONE environment setting. In various
scenarios, this is not what is used for the availability zone of a
compute node.
This change mimics the logic that's contained within the nova-compute
charm to determine which availability zone should be used for the
compute node.
Signed-off-by: Billy Olsen <billy.olsen@gmail.com>
Co-authored-by: Ionut Balutoiu <ibalutoiu@cloudbasesolutions.com>
In newer versions of Ubuntu and the Cloud Archive (currently Hirsute,
Wallaby, and above), there is an openstack-release package that, if
installed, specifies the current OpenStack release in
/etc/openstack-release.
Also adds wallaby definitions to non-version definitions in
os_versions.py.
Fixes#560
Currently the new partition test_110 is breaking on master due to the
test landing before the charm PR which implemented the change [0] has
landed.
Move the partition test to its own class which can be added as a target
in the charm's tests.yaml. This will not affect master and can be
trivially updated in [0].
[0] https://review.opendev.org/c/openstack/charm-mysql-innodb-cluster/+/779427
Do not run the deferred hooks action for neutron gateway as it is
not needed and will end in an action error.
Tested locally here: https://paste.ubuntu.com/p/cSmgxmrTr4/
This closes issue #553
If there are multiple charms of a given application then a hook
like leader-settings-changed can trigger a deferred hook. So a
race can occur where the deferred hooks of unit1 are cleared
then in the process of clearing unit2 a deferred hook is
triggerred in unit1. To fix this do not block on the wl status
message after the hook test completes.
Also, make sure that an action failure is fatal to surface any
issues.
* Add ovn-chassis test
* Yet another refactor to reduce the amount that implementations need to override.
* Add ovn dedicated chassis support
* Fix race with checking wlm
The ServiceTest.test_start_specific under the ceph osd tests stops all
services using ceph-osd.target. This will stop all the OSDs, but the
restarting of any single OSD will restart all the OSDs. This behavior
causes the charm test to fail.
Unfortunately, this wasn't caught in the initial review because the test
is skipped when there are fewer the 2 OSDs on a unit and the final test
run skipped the test due to this condition.
Fixes#542
Signed-off-by: Billy Olsen <billy.olsen@gmail.com>
* Functional test for 'enable' and 'disable' actions on nova-compute
* lint fixes
* Put tests of new functionality into separate class
* Added tests for actions `remove-from-cloud` and `register-to-cloud`
* Set longer timeout for action verification
* Add logging to help with CI debugging
* Raise error if action fails
* Cleanup running VMs before test starts
* Add cleanup to tests that create VMs
The test_vault_reload test was checking for running config without giving the
config-change time to complete. Simply adding an idle wait resolves the issue.
Closes Issue: #528
Fixes a typo (None -> not None) and renames the class from
ObjectRetrier -> ObjectRetrierWraps to make it clearer that the class
instantiation is to wrap and object with the retrier code rather than do
retries at that moment.
See https://github.com/openstack-charmers/zaza-openstack-tests/issues/530
Issue:
Python 3.5. is deprecated/EOL
Py35 is used on Xenial
Xenial is used as the test platform to run tests.
lxml is used by zaza-openstack-tests for the SAML assertions (because they are XML)
lxml > 4.6.2 releases are after py3.5 has been deprecated/EOL.
Therefore, no wheels are now built for lxml for py35.
Thus there is a binary dependency to build lxml for testing
This test shall be used for Glance testing bundles with Ceph
deployed, and multi-backend enabled.
It validates that images can be stored using the Ceph RGW (via
the OpenStack Swift API).
* Add support for running NeutronOvsVsctlTest against any charm and not
only charm-neutron-gateway.
* Add new test case for charm-neutron-gateway and charm-neutron-openvswitch to
verify correct handling of conflicting ext-port and data-port configurations.
Signed-off-by: Przemysław Lal <przemyslaw.lal@canonical.com>
