MySQL InnoDB Cluster channel 8.0.19/stable does not install 8.0.19

[Peter Colledge]

Instead latest deb package (8.0.32) is installed. Tested on both Focal & Jammy. Also affects mysql-router charm.

(Exact 8.0.19 desired as charm-vault observed failing with 8.0.32, see Bug #2004045.)

juju status --relations

Model Controller Cloud/Region Version SLA Timestamp
default lxd-controller localhost/localhost 2.9.38 unsupported 19:08:46Z

App Version Status Scale Charm Channel Rev Exposed Message
mysql-innodb-cluster 8.0.32 active 3 mysql-innodb-cluster 8.0.19/stable 24 no Unit is ready: Mode: R/O, Cluster is ONLINE and can tolerate up to ONE failure.
vault blocked 1 vault 1.7/stable 82 no Vault service not running
vault-mysql-router 8.0.32 active 1 mysql-router 8.0.19/stable 26 no Unit is ready

Unit Workload Agent Machine Public address Ports Message
mysql-innodb-cluster/0 active idle 1/lxd/0 192.168.10.29 Unit is ready: Mode: R/O, Cluster is ONLINE and can tolerate up to ONE failure.
mysql-innodb-cluster/1* active idle 1/lxd/1 192.168.10.199 Unit is ready: Mode: R/W, Cluster is ONLINE and can tolerate up to ONE failure.
mysql-innodb-cluster/2 active idle 1/lxd/2 192.168.10.219 Unit is ready: Mode: R/O, Cluster is ONLINE and can tolerate up to ONE failure.
vault/0* blocked idle 1/lxd/3 192.168.10.221 8200/tcp Vault service not running
  vault-mysql-router/0* active idle 192.168.10.221 Unit is ready

Machine State Address Inst id Series AZ Message
0 started a.example.com manual:a.example.com jammy Manually provisioned machine
1 started b.example.com manual:b.example.com jammy Manually provisioned machine
1/lxd/0 started 192.168.10.29 juju-2ab084-1-lxd-0 focal Container started
1/lxd/1 started 192.168.10.199 juju-2ab084-1-lxd-1 focal Container started
1/lxd/2 started 192.168.10.219 juju-2ab084-1-lxd-2 focal Container started
1/lxd/3 started 192.168.10.221 juju-2ab084-1-lxd-3 focal Container started

Relation provider Requirer Interface Type Message
mysql-innodb-cluster:cluster mysql-innodb-cluster:cluster mysql-innodb-cluster peer
mysql-innodb-cluster:coordinator mysql-innodb-cluster:coordinator coordinator peer
mysql-innodb-cluster:db-router vault-mysql-router:db-router mysql-router regular
vault-mysql-router:shared-db vault:shared-db mysql-shared subordinate
vault:cluster vault:cluster vault-ha peer

juju export-bundle

applications:
  mysql-innodb-cluster:
    charm: mysql-innodb-cluster
    channel: 8.0.19/stable
    revision: 24
    series: focal
    resources:
      mysql-shell: -1
    num_units: 3
    to:
    - lxd:1
    - lxd:1
    - lxd:1
    options:
      source: distro
    constraints: arch=amd64 mem=3072
  vault:
    charm: vault
    channel: 1.7/stable
    revision: 82
    series: focal
    resources:
      core: 0
      vault: 0
    num_units: 1
    to:
    - lxd:1
    constraints: arch=amd64
  vault-mysql-router:
    charm: mysql-router
    channel: 8.0.19/stable
    revision: 26
    series: focal
machines:
  "1":
    series: jammy
relations:
- - vault:shared-db
  - vault-mysql-router:shared-db
- - vault-mysql-router:db-router
  - mysql-innodb-cluster:db-router

[Alex Kavanagh (ajkavanagh)]

Hi Peter

The 8.0.19 is a legacy channel that shouldn't be used. We've not deleted it (yet) as there are a few systems that are running the 8.0.19 charm, that still need to be switched.

However, it is confusing; The track name indicates what the charm supports, not what it actually installs. Due to the way machine charms work, the distro (or cloud archive) packages actually determine what is installed. On focal and jammy (at the time of writing) this is the 8.0.32. And the charmhub channel that supports that is 8.0.

So in summary; please use the 8.0/stable track for mysql-innodb-cluster and mysql-router on focal (20.04 LTS) and jammy (22.04 LTS)