Cluster setup stuck
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL InnoDB Cluster Charm |
In Progress
|
High
|
Liam Young |
Bug Description
Deploying the cluster gets stuck with units in the following state:
mysql-innodb-
mysql-innodb-
mysql-innodb-
The lead unit has the following error in the juju unit log:
2020-05-05 06:39:34 ERROR juju-log Failed adding instance 172.20.0.19 to cluster: Logger: Tried to log to an uninitialized logger.
^[[31mERROR: ^[[0mInstance '172.20.0.19:3306' is part of the Group Replication group but is not in the metadata. Please use <Cluster>.rescan() to update the metadata.
Traceback (most recent call last):
File "<string>", line 3, in <module>
SystemError: RuntimeError: Cluster.
2020-05-05 06:39:34 INFO juju-log Adding instance, 172.20.0.27, to the cluster.
2020-05-05 06:39:34 ERROR juju-log Failed adding instance 172.20.0.27 to cluster: Logger: Tried to log to an uninitialized logger.
^[[31mERROR: ^[[0mInstance '172.20.0.27:3306' is part of the Group Replication group but is not in the metadata. Please use <Cluster>.rescan() to update the metadata.
Traceback (most recent call last):
File "<string>", line 3, in <module>
SystemError: RuntimeError: Cluster.
Changed in charm-mysql-innodb-cluster: | |
importance: | Undecided → High |
assignee: | nobody → Liam Young (gnuoy) |
status: | New → Confirmed |
Fix proposed to branch: master /review. opendev. org/725529
Review: https:/