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 1.7/edge channel doesn't support Bionic, so this change updates the
bionic bundles to deploy using the 1.6/edge channel which is the last
track that has support for Ubuntu 18.04.
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.
The charm is polluting the system it is installed on causing bug #1970230. All reactive charms should use a venv wherever
possible and I belive it is just an oversight that this one
does not.
Closes-Bug: #1970230
Change-Id: I3bb162c5a10735c6c4402069719d13c5c2037bf7
(cherry picked from commit 9fb3530b0c9c065afb12ac7f3b46ec959b1cb55b)
* 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
