Starting with the release of Wallaby, the 'tgtadm' package is
now the default target helper, which doesn't work for cinder-lvm.
As such, we need to explicitly set the new package to 'lioadm'.
Also bumps PyYAML dep to 6.0.1 to fix build error
Closes-Bug: #1949074
Change-Id: I4d88d1e30d8b2b133bd575a76d0dc5e566415cbc
(cherry picked from commit 3144ea032b35842db6f62bbb26aef9c68a6226a6)
(cherry picked from commit 3b04e42f31a9638858c7f6fa11215090175e4681)
Update src/build.lock to get the latest revision available in the
stable/antelope branch, among the most relevant patches are:
837a8b58 Support legacy cert requests (#799)
580c7764 Update Makefile to be consistent with CI (#777) (#795)
a2468260 Run CI on stable branches (#786) (#787)
ed014373 Update method for checking endpoint protocol (#769) (#775)
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
* Drop 'source' override for mysql-innodb-cluster and rabbitmq-server
Change-Id: Id91cfd716811ae245b27fd581c64cb17ee51c921
(cherry picked from commit e77c9a0c66d63af7622b18f1f9458bbfa3b37786)
The build log for the charm on launchpad ends up with src already
existing which means that the mkdir failed. Change it to a mkdir -p src
and just touch/make the file executable to try to change anything that
might be there.
Build separately for each supported series and use binary builds
Charms for OpenStack Yoga supports both Ubuntu Focal and Jammy
which means Python 3.8 and Python 3.10. Managing dependencies
across those two versions is non-trivial and we need to build
the charm on the series the charm is supposed to support.
Switch to using a binary build which allows pip's dependency
resolution to work.
* 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
