[ussuri] Ensure get_requests_for_local_unit doesn't fail on incomplete relation
This is a rebuild/make sync for charms to pickup the fix in charmhelpers to fix
any inadvertant accesses of ['ca'] in the relation data before it is available
from vault in the certificates relation. Fix in charmhelpers is in [1].
Ensure the RabbitMQ oslo.messaging section is used in all templates;
this configures SSL options when deployed in TLS secured configurations
with RabbitMQ.
Change-Id: I0821304b3f0e586e3a868e3c95294a688bae085a
Closes-Bug: 2007567
(cherry picked from commit f4a8f7c4dfc5a5ef0244b095b7ea83d1e78e99d0)
Due to bug #2025085, the functional tests fail when attempting
to resolve the hacluster and pacemaker-remote charms for the
bionic series. This can be worked-around by providing a series
specifically for the application specified in the bundle.
The build.lock branch points to master which means that the layer is not
locked. Lock the layers to the commit hash instead; this ensures
reproducible builds as much as possible.
* use stable/21.10 libraries
* use zaza/zaza-openstack-tests at stable/21.10
* build.lock files for reactive charms
* bundles refer to ~openstack-charms candidate channel
* update tox/pip.sh to ensure setuptools<50.0.0
Specify certificates relation to update endpoints.
When the certificates relation is unspecified with the
configure_tls method invocation, the masakari endpoints
seem to ignore the update to TLS. This change specifies
the relation which causes the endpoints to update correctly.