Cluster is inaccessible from this instance

charm
,
1

We suffered a power outage again, I have been able to get back our OpenStack cluster many times before, but this time I can start the master using the leader node, but the slaves never join after using: STOP GROUP_REPLICATION; RESET SLAVE;

The current juju status is :

https://paste.ubuntu.com/p/9wxymMCpbd/

I cant use reset slave with mysql-innodb-cluster/2 I got this error 2024-02-06T19:00:47.611589Z 0 [System] [MY-011504] [Repl] Plugin group_replication reported: ‘Group membership changed: This member has left the group.’

2

I manage to get one more node working , jost one is misisng with the following errors

2024-02-06T22:34:38.831543Z 24 [System] [MY-010597] [Repl] ‘CHANGE REPLICATION SOURCE TO FOR CHANNEL ‘group_replication_recovery’ executed’. Previous state source_host=‘10.2.101.149’, source_port= 3306, source_log_file=‘’, source_log_pos= 4, source_bind=‘’. New state source_host=‘10.2.101.153’, source_port= 3306, source_log_file=‘’, source_log_pos= 4, source_bind=‘’. 2024-02-06T22:34:38.837902Z 31 [Warning] [MY-010897] [Repl] Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the ‘START REPLICA Syntax’ in the MySQL Manual for more information. 2024-02-06T22:34:38.853040Z 31 [System] [MY-014002] [Repl] Replica receiver thread for channel ‘group_replication_recovery’: connected to source ‘mysql_innodb_cluster_1002@10.2.101.153:3306’ with server_uuid=df69dccd-9b3c-11ec-a276-00163e96d3c5, server_id=1000. Starting GTID-based replication. 2024-02-06T22:34:38.886312Z 33 [ERROR] [MY-010584] [Repl] Replica SQL for channel ‘group_replication_recovery’: Worker 1 failed executing transaction ‘7d734394-9b3d-11ec-8fec-00163e96d3c5:671171873’ at source log binlog.005060, end_log_pos 24988952; Could not execute Update_rows event on table vault.vault; Can’t find record in ‘vault’, Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event’s source log binlog.005060, end_log_pos 24988952, Error_code: MY-001032 2024-02-06T22:34:38.886943Z 32 [ERROR] [MY-010586] [Repl] Error running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with “START REPLICA”. We stopped at log ‘binlog.005060’ position 24987415