- Improved docs for remove-instance action
in light of bugs LP#1954306 and LP#2006759
- Fixed exception handling of failed configure
step of add-instance action, which resulted in
bug LP#1983158
- Fixed exception handling which
was raising a new exception instead
of reraising the existing one.
Actions such as remove-instance and add-instance
cause leader-settings updates, which in turn result
in flag updates that are later checked in actions
and hooks. However, a hook is required to run after
an action to apply the leader-settings updates into
the flags, causing issues when actions are run
without a hook in-between.
This patch addresses that by changing the flag
checks to leader-settings checks, so it is
always using the most up-to-date information
and preventing the issue.
When creating a backup of a database, the --set-gtid-purged settin must
be set to OFF if the dump is to be restored on a different MySQL
cluster. This change creates a knob in the mysql dump action of the
charm that allows setting this option to one of the supported values.
Closes-Bug: #2040159
Change-Id: Ide1b222c36edbe65de123a57630fe3dc24c4d6b6
Signed-off-by: Gabriel Adrian Samfira <email address hidden>
Add the 'docs' key and point it at a Discourse topic
previously populated with the charm's README contents.
When the new charm revision is released to the Charmhub,
this Discourse-based content will be displayed there. In
the absense of the this new key, the Charmhub's default
behaviour is to display the value of the charm's
'description' key.
The full-model CI jobs deploy a complete OpenStack cloud in HA, although
the tests.yaml doesn't include any extra testing, so far this testing
hasn't shown any benefits.
This patch drops those CI jobs and updates focal and jammy jobs to
deploy Keystone in HA, as a way to still have a HA related application
to mysql-innodb-cluster.
