This (stable) branch was cut originally to support the
mysql-innodb-cluster charm with the "20.04" base, although due to a
series of events to simplify the management it was decided to use the
stable/jammy git branch to source the `8.0` charmhub track and provide a
charm capable of running on "20.04" and "22.04".
mysqldump: add --set-gtid-purged=COMMENTED to mysqldump command
The backup file taken from a charm-managed mysql instance contains
"@@GLOBAL.GTID_PURGED" variable at the beginning, which causes
restore operation to fail with the following message: "Cannot
update GTID_PURGED with the Group Replication plugin running".
The workaround for this issue is to supply "--set-gtid-purged=OFF"
to command, which omits the "GTID_PURGED" from the mysqldump output.
This patch fixes the issue by adding "--set-gtid-purged=COMMENTED"
to mysqldump command, which causes mysqldump to emit the GTID_PURGED
variable as a commented out line. In this way, we don't lose the
GTID_PURGED variable information which may be needed in some scenarios
and can be un-commented out before restoring if needed.
Closes-bug: 1989975
Change-Id: Ie3b71a60e4c7afda48114a53cce9cf713b933d71
(cherry picked from commit 82ebc349fab662d65366fa5958669d653958eaf8)
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.
Additional changes include:
- Add bindep.txt changes from origin/master by hand.
- Switch charm-tools to 2.8.5 to remove ruamel requirement that
doesn't work on Python 3.10.
- Pin zipp<=1.2.0, zipp >1.2.0. require setuptools>=42 (41.6.0 available atm)
Related-Bug: #2002788
Change-Id: If5e5beda90a918e8ff48f1d47fc91d90d79d27fe
Signed-off-by: Mustafa Kemal Gilor <email address hidden>
The 'focal' batch includes charms that are distro based, rather than
OpenStack release based.
Note: this has a modified charmcraft.yaml to work with bionic / tox
needs to be 3.18 (bionic comes with 2.5), so tox is pip installed as
user in the charmcraft lxd.
The charmcraft build use 18.04 (bionic) to build on, but the charm will
run on 18.04 and 20.04. This is so that the charm can be used to series
upgrade from bionic to focal.
* 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
The openstack-principle reactive layer brings both the
openstack-origin option and the openstack-upgrade
action, none of which being needed for this charm.
This layer has been used already since the very first
commit of this charm, most likely for no specific
reason.
