Set container-infra API version to 1.9 for >=Ussuri,<=Wallaby.
Horizon needs to use container-infra 1.9 version, the openstack
client's default, to be able to resize k8s clusters, but by default
Horizon uses 1.1 until Xena ( https://opendev.org/openstack/magnum-ui/commit/1fc627fb ).
This change sets OPENSTACK_API_VERSIONS['container-infra'] to 1.9 for
U/V/W, and unsets the key for >=Xena
Closes-Bug: #1998509
Change-Id: Ie358e9c115273ae648c9bef2aedaae50e5ee179d
(cherry picked from commit c3527010b59dccf0c0c49c8494f4ed1273972669)
Tox 4.0.0 was recently released and it has several breaking changes.
We pin to < 4.0.0 here. We are planning to move forward only on the
master charm branches.
Tox is also pinned to < 4.0.0 for stable branches in upstream
openstack-zuul-jobs as well as in zosci-config. However, the
requires= section in the charm's tox.ini file ends up installing
tox>4, wiping out the zuul-pinned tox<4 that was already installed
installed. This patch fixes that.
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
