mysql-innodb-cluster/0* blocked executing 0/lxd/3 192.168.221.99 MySQL InnoDB Cluster not healthy: None
mysql-innodb-cluster/1 blocked idle 1/lxd/2 192.168.221.5 MySQL InnoDB Cluster not healthy: None
mysql-innodb-cluster/2 blocked idle 2/lxd/2 192.168.221.8 MySQL InnoDB Cluster not healthy: None
The whole cloud is bust because mysql-innodb-cluster is not up. The vault charm *has* a bug in that it is erroring because it can't talk to mysql, but that will resolve when the mysql cluster comes up. That's what you need to concentrate on. Once mysql is back, everything should sort itself out.
Please reach out on IRC (OFTC #openstack-charms) or the discourse for charmhub (https://discourse.charmhub.io/) if you need help getting the mysql cluster back up. The bug here is that the ergonomics of the vault charm aren't handling the absent mysql cluster properly.
Ah, okay, the key issue is this:
mysql-innodb- cluster/ 0* blocked executing 0/lxd/3 192.168.221.99 MySQL InnoDB Cluster not healthy: None cluster/ 1 blocked idle 1/lxd/2 192.168.221.5 MySQL InnoDB Cluster not healthy: None cluster/ 2 blocked idle 2/lxd/2 192.168.221.8 MySQL InnoDB Cluster not healthy: None
mysql-innodb-
mysql-innodb-
The whole cloud is bust because mysql-innodb- cluster is not up. The vault charm *has* a bug in that it is erroring because it can't talk to mysql, but that will resolve when the mysql cluster comes up. That's what you need to concentrate on. Once mysql is back, everything should sort itself out.
Please reach out on IRC (OFTC #openstack-charms) or the discourse for charmhub (https:/ /discourse. charmhub. io/) if you need help getting the mysql cluster back up. The bug here is that the ergonomics of the vault charm aren't handling the absent mysql cluster properly.