Recovering a bad cluster fails with charm actions

Bug #1997227 reported by Diko Parvanov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL InnoDB Cluster Charm
Triaged
Wishlist
Unassigned

Bug Description

Trying to run rejoin-cluster or join-cluster charm actions fail with getting authentication issues on the unit I tried to add, I had to manually recover that unit with the following commands:

STOP GROUP_REPLICATION \W;
SET GLOBAL super_read_only = 0;
CLONE INSTANCE FROM 'clusteruser'@'<ANY_WORKING_MEMBER>':3306 IDENTIFIED BY 'CLUSTER_PASSWORD' REQUIRE SSL;

Then in mysqlsh on the master:

shell.connect('clusteruser:PWD@MASTER_IP')
cluster = dba.get_cluster()
cluster.add_instance('clusteruser:PWD@<INSTANCE_TO_BE_ADDED_IP>')

Is it possible to add this functionality to the charm?

Changed in charm-mysql-innodb-cluster:
status: New → Triaged
importance: Undecided → Wishlist
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.