[2023.1] 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].
This patch is to lock the stable/2023.1 (antelope release) charms
down so that as much as possible.
In particular, this patch does:
- set the .gitreview to stable/2023.1
- lock zaza and zaza-openstack-tests to stable/antelope branches
- for reactive charms Add build.lock files to lock the layers
and python modules used to build the charm.
- for ops framework charms, extract a pip freeze from the
charmcraft container after building the charm to lock the
modules used to build the charm.
- drop the kinetic bundles if the exist. (Note the updates to
tests.yaml is in another batch (topic: antelope-voting)
- update the bundles so that they point to the antelope specific
channels. e.g. 2023.1/edge for OpenStack charms, 23.03/edge for
OVN charms, quincy/edge for Ceph charms and generally, the
appropriate LTS Jammy branch for the various support charms.
Enable jammy-antelope voting and drop kinetic-zed tests
* Voting was turned on for jammy-antelope in the
project-template for charm-functional-jobs in zosci-config
* Voting for jammy-antelope bundles with non-standard names
is turned on in individual charms
* Kinetic-zed bundles/tests are removed
* Add libpython3-dev to allow the charm to be built. This
fixes a missing dependency with Cython
Change-Id: I83b97c35b6e64050feaa94a2eee2b80fa49c2555
(cherry picked from commit ea96987f114be44d5d0fac2fb80692245b601ee7)
* sync charm-helpers to classic charms
* change openstack-origin/source default to zed
* align testing with zed
* add new zed bundles
* add zed bundles to tests.yaml
* add zed tests to osci.yaml and .zuul.yaml
* update build-on and run-on bases
* add bindep.txt for py310
* sync tox.ini and requirements.txt for ruamel
* use charmcraft_channel 2.0/stable
* drop reactive plugin overrides
* move interface/layer env vars to charmcraft.yaml
Using the sql_connection option in the default section appears to
cause CONF.api_database.connection to be populated with the
connection uri. This in turn causes nova to think this is an
api cell and to do an api lookup *1 which fails. This change moves
the database connection string into its own section as per *2
Updates to enable jammy and finalise charmcraft builds
- Add 22.04 to charmcraft.yaml
- Update metadata to include jammy
- Remove impish from metadata
- Update osci.yaml to include py3.10 default job
- Modify tox.ini to remove py35,py36,py37 tox target and add py310
target.
- ensure that the openstack-origin is yoga
- Remove overlay as no longer needed in charmhub with explicit .charm
- Pin setuptools < 50.0 in src/wheelhouse.txt
