[train] 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].
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.
This is the main patch for the migration of the stable/21.10
charm to charmhub for the stable/train branch (train track on
charmhub). This patch initially supports bionic from queens
to train, and does not support ussuri. It supports upgrades
from bionic-queens to bionic-train (with each intermediate
step needed). Crucially it does NOT set a default
openstack-origin, which means installing train/stable
without specifying the openstack-origin will result in a
bionic-queens installation. This is intentional as the branch
covers queens to train.
* 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.
Without this fix deployment fails with
ERROR cannot deploy bundle: cannot add unit for
application "masakari": acquiring machine to host
unit "masakari/0": cannot assign unit "masakari/0"
to machine 12: series does not match