Cluster setup stuck

Bug #1876861 reported by Liam Young
6
This bug affects 1 person
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-cluster/0* waiting idle 8 172.20.0.4 Not all instances clustered
mysql-innodb-cluster/1 waiting idle 9 172.20.0.19 Instance not yet in the cluster
mysql-innodb-cluster/2 waiting idle 10 172.20.0.27 Instance not yet in the cluster

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.add_instance: Metadata inconsistent

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.add_instance: Metadata inconsistent

Liam Young (gnuoy)
Changed in charm-mysql-innodb-cluster:
importance: Undecided → High
assignee: nobody → Liam Young (gnuoy)
status: New → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-mysql-innodb-cluster (master)

Fix proposed to branch: master
Review: https://review.opendev.org/725529

Changed in charm-mysql-innodb-cluster:
status: Confirmed → In Progress
Revision history for this message
Liam Young (gnuoy) wrote :

The functional tests of the following pr hit this issue. The crashdump shows the error in the logs of the mysql-innodb-cluster_0 unit

https://openstack-ci-reports.ubuntu.com/artifacts/test_charm_pipeline_func_full/openstack/charm-masakari-monitors/723613/5/5540/index.html

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on charm-mysql-innodb-cluster (master)

Change abandoned by Liam Young (<email address hidden>) on branch: master
Review: https://review.opendev.org/725529

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.