This test is unstable, increasing the logging from debug to info allows
to the CI runs to expose more information and understand what part of
the test is staying blocked and leading the CI job to time out.
Related-Bug: http://pad.lv/2003775
There is a race in the 408 test for rabbitmq where the config-change to
enable ssl causes a leader-settings-changed hook in the non-leader units
which results in a rabbitmq service restart. This can happen at exactly
the same time as the test attempts to establish a connection with the
that unit. This patch retries the connection attempt.
Note that this may only be a partial fix as it's possible that a restart
will happen just after the connection is made, which would then result
in a test failure.
Related-Bug: LP#2002156
There are scenarios where the config-changed hook can complete, yet the
service IP get configured many seconds after, because a relation-changed
hook execution needs to be triggered on the hacluster side of the
relation.
This change adds a retry to the check (10 times with a 2 seconds wait
time).
This issue was found at the gate https://review.opendev.org/c/openstack/charm-designate-bind/+/861417
The create_segment() function is often failing in the gate
due to being unable to establish a connection to the masakari
endpoint. This will allow some more time for the endpoint to
become available when this error occurs.
nosetest doesn't support python 3.10 and over the years the python
community has been settling on pytest as test runner, this change
introduces pytest and adds py3.10 to the gh workflow testing matrix.
In some testing environment, `wait_for_application_states()` can
execute before juju starts actually performing changes on the
units, causing it to return immediately.
Add test class that runs tempest in miminal mode. This is useful
for testing that the OpenStack apis are responding but there are
components not configured like an external network. In addtion
some missing doc strings were added and support for neutron
tempest configuration pre ussuri removed as there is a branch
for that.
* Add method to check OpenStack endpoints
Add method to check OpenStack endpoints are returning acceptable
http codes. This should be used with caution as a charm whould
indicate if its payload is not ready via workload status and
workload status messages
* Fix dox string
When creating Openstack VMs the user has to specify the image it wants
to use. sstream-mirror-glance adds a date to the image name, so they
always have to recheck which is the current latest image.
This commit tests the usage of the `set_latest_property` configuration.
When --set-latest-property is given sstream-mirror-glance will set the
recently synced image with the `latest=true` property and then remove
the `latest` property from all the os_version/architecture matching
images.
Closes-bug: LP #1933130