I have a mysql-innodb-cluster from some time back, which I now can’t refresh because it appears that the charm’s channel name has changed (from ‘stable’ to ‘8.0/stable’).
$ juju refresh mysql-innodb-cluster
ERROR not found
Can I change the channel name for an installed charm somehow? Did I miss something?
Are you actually using channels with the mysql-innodb-cluster charm? What is the output to:
juju status mysql-innodb-cluster@pmatulis apologies I neglected to check back here. Thanks for responding.
I get different output for my long-standing model and a fresh openstack-base install.
The long-standing model looks like this;
routergod@juju:~$ juju status mysql-innodb-cluster
Model Controller Cloud/Region Version SLA Timestamp
openstack production openstack-maas/default 2.9.32 unsupported 11:15:02+01:00
App Version Status Scale Charm Channel Rev Exposed Message
mysql-innodb-cluster 8.0.28 active 4 mysql-innodb-cluster stable 15 no Unit is ready: Mode: R/O, Cluster is ONLINE and can tolerate up to ONE failure.
Unit Workload Agent Machine Public address Ports Message
mysql-innodb-cluster/0 active idle 3/lxd/6 10.23.130.15 Unit is ready: Mode: R/O, Cluster is ONLINE and can tolerate up to ONE failure.
mysql-innodb-cluster/1 active idle 1/lxd/6 10.23.130.25 Unit is ready: Mode: R/O, Cluster is ONLINE and can tolerate up to ONE failure.
mysql-innodb-cluster/2 active idle 2/lxd/6 10.23.130.40 Unit is ready: Mode: R/O, Cluster is ONLINE and can tolerate up to ONE failure.
mysql-innodb-cluster/4* active idle 5/lxd/2 10.23.130.208 Unit is ready: Mode: R/W, Cluster is ONLINE and can tolerate up to ONE failure.
Machine State Address Inst id Series AZ Message
1 started 10.23.130.2 control01 focal default Deployed
1/lxd/6 started 10.23.130.25 juju-7008a6-1-lxd-6 focal default Container started
2 started 10.23.130.3 control02 focal default Deployed
2/lxd/6 started 10.23.130.40 juju-7008a6-2-lxd-6 focal default Container started
3 started 10.23.130.5 control03 focal default Deployed
3/lxd/6 started 10.23.130.15 juju-7008a6-3-lxd-6 focal default Container started
5 started 10.23.130.6 compute00 focal default Deployed
5/lxd/2 started 10.23.130.208 juju-7008a6-5-lxd-2 focal default Container started
A fresh openstack-base looks like this now;
routergod@juju:~$ juju status mysql-innodb-cluster
Model Controller Cloud/Region Version SLA Timestamp
teststack production openstack-maas/default 2.9.32 unsupported 11:14:04+01:00
App Version Status Scale Charm Channel Rev Exposed Message
mysql-innodb-cluster 8.0.30 active 3 mysql-innodb-cluster 8.0/stable 26 no Unit is ready: Mode: R/O, Cluster is ONLINE and can tolerate up to ONE failure.
Unit Workload Agent Machine Public address Ports Message
mysql-innodb-cluster/0 active idle 0/lxd/4 10.23.131.179 Unit is ready: Mode: R/O, Cluster is ONLINE and can tolerate up to ONE failure.
mysql-innodb-cluster/1 active idle 1/lxd/3 10.23.131.169 Unit is ready: Mode: R/O, Cluster is ONLINE and can tolerate up to ONE failure.
mysql-innodb-cluster/2* active idle 2/lxd/2 10.23.131.173 Unit is ready: Mode: R/W, Cluster is ONLINE and can tolerate up to ONE failure.
Machine State Address Inst id Series AZ Message
0 started 100.127.128.14 teststack01 focal default Deployed
0/lxd/4 started 10.23.131.179 juju-14a134-0-lxd-4 focal default Container started
1 started 100.127.128.6 teststack02 focal default Deployed
1/lxd/3 started 10.23.131.169 juju-14a134-1-lxd-3 focal default Container started
2 started 100.127.128.7 teststack03 focal default Deployed
2/lxd/2 started 10.23.131.173 juju-14a134-2-lxd-2 focal default Container startedYour first paste describes a model that is using non-channel charms. The second paste describes one that is making use of channel charms.
You can migrate to channel charms if you want. The procedure for doing so is described on the All charms: migration to channels page.
Thank you, I’ve learned something.
routergod@juju:~$ juju refresh --switch ch:mysql-innodb-cluster --channel=8.0/stable mysql-innodb-cluster
Added charm-hub charm "mysql-innodb-cluster", revision 30 in channel 8.0/stable, to the model
Adding endpoint "db-monitor" to default space "internal"
Leaving endpoints in "internal": certificates, cluster, coordinator, db-router, shared-db