Mysql Router
- MySQL Charm Maintainers
- Cloud
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/edge | 256 | 16 Oct 2024 | |
| latest/edge | 255 | 16 Oct 2024 | |
| latest/edge | 254 | 16 Oct 2024 | |
| latest/edge | 253 | 16 Oct 2024 | |
| latest/edge | 201 | 19 Jun 2024 | |
| latest/edge | 108 | 12 Sep 2023 | |
| latest/edge | 62 | 10 Feb 2023 | |
| 8.0/stable | 257 | 17 Oct 2024 | |
| dpe/candidate | 225 | 28 Aug 2024 | |
| dpe/candidate | 224 | 28 Aug 2024 | |
| dpe/candidate | 223 | 28 Aug 2024 | |
| dpe/beta | 225 | 23 Aug 2024 | |
| dpe/beta | 224 | 23 Aug 2024 | |
| dpe/beta | 223 | 23 Aug 2024 | |
| dpe/edge | 260 | 25 Oct 2024 | |
| dpe/edge | 259 | 25 Oct 2024 | |
| dpe/edge | 258 | 25 Oct 2024 | |
| 8.0.19/stable | 26 | 05 May 2022 | |
| 8.0.19/edge | 26 | 05 May 2022 | |
| 8.0.19/edge | 15 | 26 Apr 2022 |
juju deploy mysql-router --channel dpe/candidate
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
24.04
23.10
23.04
22.10
22.04
21.10
21.04
20.10
20.04
Charm Statuses
WARNING : it is an work-in-progress article. Do NOT use it in production! Contact Canonical Data Platform team if you are interested in the topic.
The charm follows standard Juju applications statuses. Here you can find the expected end-users reaction on different statuses:
| Juju Status | Message | Expectations | Actions |
|---|---|---|---|
| active | any | Normal charm operations | No actions required |
| waiting | any | Charm is waiting for relations to be finished | No actions required |
| maintenance | any | Charm is performing the internal maintenance (e.g. re-configuration) | No actions required |
| blocked | any | The manual user activity is required! | Follow the message hints (see below) |
| blocked | Missing relation: … | Normal behavior, charm needs all relations to work. | Follow the hint to establish a proper relation. |
| blocked | Router was manually removed from MySQL ClusterSet. Remove & re-deploy unit | Scale-down temporary message OR split-brain for the unknown reason. | Wait to finish scale-down or remove and re-deploy unit if the message is persistent. |
| blocked | … app requested unsupported extra user role on database endpoint | Unsupported role requested. | Use supported extra-user-role. |
| blocked | Upgrade incompatible. Rollback to previous revision with juju refresh
|
Incompatible charm channel/revision chosen. | Rollback the charm. |
| blocked | Upgrading. Verify highest unit is healthy & run resume-upgrade action. To rollback, juju refresh to last revision |
Normal behavior, application is being upgraded and waiting for user confirmation to continue or rollback | Continue upgrade or rollback. |
| error | any | An unhanded internal error happened | Read the message hint. Execute juju resolve <error_unit/0> after addressing the root of the error state |
| terminated | any | The unit is gone and will be cleaned by Juju soon | No actions possible |
| unknown | any | Juju doesn’t know the charm app/unit status. Possible reason: the charm termination in progress. | Manual investigation required if status is permanent |