* 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>
The main failure that seems to occur with clients is the
ConnectFailure, which according to the docs, is retry-able. Thus
provide a function that adds that exception condition automatically.
Also fix the import problem in octavia test for the object retrier that
is being used to validate the ObjectRetrier feature.
This adds a wrapper class that detects if a callable object in any of
the descendent objects raises an Exception. If so, then it retries that
exception.
This is to attempt to make the zaza tests a little more robust in the
face of small network failures or strange restarts. This is a test, and
robust logging a reporting should be used to determine whether it is
covering up actual bugs rather than CI system issues.
Related Bug: (zot repo)#348
* Fix the kerberos set-up by loosening ubuntu check
The cs:ubuntu charm's workload-status-message has changed recently (as
the charm was re-written). This PR loosens the application states check
to ignore the workload-status-message and just wait for the charm to be
active workload-status. This is almost certainly enough, as it's a very
simple charm.
* Fix tox.ini to pass tests (maybe)
The test was failing for xenial-ha-mysql bundle
This fixes the issue for cluster vault
by picking the right vault cluster leader
to run the commands against.
Co-authored-by: Bartosz Woronicz <bartosz.woronicz@canonical.com>
The current Manila Ganesha `test_manila_share` had a lot of
functionality that can be re-used to any configured Manila backend.
It's a good idea to have this functionality generalized into
`zaza.manila.tests.ManilaBaseTest`, which can be reused for any
tested Manila backend.
* Move general function out of the testing class. This will make them
easy to be reused.
* Properly organize the tests, and add tons of docstrings and comments
to have them as clear as possible.
* Add `failover_cinder_volume_host` to the Zaza `utilities/openstack.py`,
since this is a general purpose function.
Removing and re-adding two units out of a cluster of three
so fast seems to be too stressful for corosync/pacemaker,
which makes the test fail in rare cases. Removing and
re-adding one unit only is enough in order to validate the
functionality. This also makes the test execution time
much shorter.
The automatic corosync cleanup on Juju >= 2.8 turned out
not to work and has been removed from charm-hacluster.
The 'update-ring' action is now always needed.
The updated tests add the possibility of testing deployments
with `image` RBD mirroring mode implemented as part of the
Cinder Ceph Replication charm spec.
