|8.0/stable||196||29 Sep 2023|
|8.0/candidate||196||27 Sep 2023|
|8.0/beta||196||25 Sep 2023|
|8.0/edge||203||01 Dec 2023|
juju deploy mysql --channel 8.0/stable
Example: MySQL 8.0.34 -> MySQL 8.0.33
(including simple charm revision bump: from revision 43 to revision 42)
Minor rollback steps
- Prepare “Charmed MySQL” Juju application for the in-place rollback. See the step description below for all technical details executed by charm here.
- Rollback. Once started all units in a cluster will be executed sequentially. The rollback will be aborted (paused) if the unit rollback has failed.
- Check. Make sure the charm and cluster are in healthy state again.
juju refresh, case there any version incompatibilities in charm revisions or it dependencies, or any other unexpected failure in the upgrade process, the upgrade process will be halted an enter a failure state.
Although the underlying MySQL Cluster continue to work, it’s important to rollback the charm to previous revision so an update can be later attempted after a further inspection of the failure.
To execute a rollback we take the same procedure as the upgrade, the difference being the charm revision to upgrade to. In case of this tutorial example, one would refresh the charm back to revision
182, the steps being:
Step 1: Prepare
It is necessary to re-run
pre-upgrade-check action on the leader unit, to enter the upgrade recovery state:
juju run-action mysql/leader pre-upgrade-check --wait
Step 2: Rollback
When using charm from charmhub:
juju refresh mysql --revision=182
Case deploying from local charm file, one need to have the old revision charm file and run:
juju refresh mysql --path=./mysql_ubuntu-22.04-amd64.charm
mysql_ubuntu-22.04-amd64.charm is the previous revision charm file.
The first unit will be rolled out and should rejoin the cluster after settling down. After the refresh command, the juju controller revision for the application will be back in sync with the running Charmed MySQL revision.