Mysql-innodb-cluster recover broken cluster

Hey,

our mysql innodbcluster seems totally broken, we only have one active unit which is okay in terms that we can still use our openstack deployment even tho it has no failover, we tried rejoining, add-instances and first of all we tried the reboot-cluster-from-complete outage action, but we cant get all three to work, in out testing environment we had no problems at all. And we are really frustrated now… It would be extremely awesome if we could get some help.

We also tried adding a new unit and adding this unit to the pre existing cluster, but this did not work

No we have one unit in an error state with

hook failed: "cluster-relation-departed"

and one in the block state with

 Cluster is inaccessible from this instance. Please check logs for details.

Unit in Error state /var/log/mysql/error.log

2022-03-18T15:10:34.915404Z 0 [ERROR] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Error on opening a connection to peer node 172.16.58.101:33061 when joining a group. My local port is: 33061.'
2022-03-18T15:10:34.915451Z 0 [ERROR] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Error connecting to all peers. Member join failed. Local port: 33061'
2022-03-18T15:10:34.970383Z 0 [ERROR] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] The member was unable to join the group. Local port: 33061'
2022-03-18T15:10:38.532322Z 2 [ERROR] [MY-011640] [Repl] Plugin group_replication reported: 'Timeout on wait for view after joining group'
2022-03-18T15:10:38.532436Z 2 [ERROR] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] The member is already leaving or joining a group.'
2022-03-18T15:16:59.774179Z 4670 [System] [MY-013587] [Repl] Plugin group_replication reported: 'Plugin 'group_replication' is starting.'
2022-03-18T15:16:59.775731Z 4670 [Warning] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Automatically adding IPv4 localhost address to the allowlist. It is mandatory that it is added.'
2022-03-18T15:16:59.775753Z 4670 [Warning] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Automatically adding IPv6 localhost address to the allowlist. It is mandatory that it is added.'
2022-03-18T15:16:59.804045Z 4675 [System] [MY-010597] [Repl] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_applier' executed'. Previous state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''.
2022-03-18T15:16:59.820634Z 4677 [ERROR] [MY-010596] [Repl] Error reading relay log event for channel 'group_replication_applier': corrupted data in log event
2022-03-18T15:16:59.820680Z 4677 [ERROR] [MY-013121] [Repl] Slave SQL for channel 'group_replication_applier': Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, the server was unable to fetch a keyring key required to open an encrypted relay log file, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Error_code: MY-013121
2022-03-18T15:16:59.820703Z 4677 [ERROR] [MY-011451] [Repl] Plugin group_replication reported: 'The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.'
2022-03-18T15:16:59.820741Z 4675 [ERROR] [MY-011452] [Repl] Plugin group_replication reported: 'Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.'
2022-03-18T15:16:59.820797Z 4675 [ERROR] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] The member is leaving a group without being on one.'
2022-03-18T15:16:59.820820Z 4675 [ERROR] [MY-011644] [Repl] Plugin group_replication reported: 'Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.'
2022-03-18T15:16:59.820834Z 4675 [ERROR] [MY-011712] [Repl] Plugin group_replication reported: 'The server was automatically set into read only mode after an error was detected.'
2022-03-18T15:16:59.820955Z 4677 [ERROR] [MY-010586] [Repl] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'FIRST' position 0
2022-03-18T15:17:01.048055Z 0 [ERROR] [MY-011502] [Repl] Plugin group_replication reported: 'There was a previous plugin error while the member joined the group. The member will now exit the group.'
2022-03-18T15:17:01.048122Z 0 [System] [MY-011503] [Repl] Plugin group_replication reported: 'Group membership changed to 172.16.58.79:3306 on view 16476166099420298:2.'
2022-03-18T15:17:01.048160Z 0 [ERROR] [MY-011486] [Repl] Plugin group_replication reported: 'Message received while the plugin is not ready, message discarded.'
2022-03-18T15:17:04.126291Z 0 [System] [MY-011504] [Repl] Plugin group_replication reported: 'Group membership changed: This member has left the group.'
2022-03-18T15:33:29.182121Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user <via user signal>. Shutting down mysqld (Version: 8.0.28-0ubuntu0.20.04.3).
2022-03-18T15:33:31.712269Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.28-0ubuntu0.20.04.3)  (Ubuntu).
2022-03-18T15:38:08.335817Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.28-0ubuntu0.20.04.3) starting as process 456
2022-03-18T15:38:08.352745Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-03-18T15:38:08.684579Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2022-03-18T15:38:08.883793Z 0 [System] [MY-013587] [Repl] Plugin group_replication reported: 'Plugin 'group_replication' is starting.'
2022-03-18T15:38:08.956712Z 0 [Warning] [MY-010068] [Server] CA certificate /etc/ssl/certs/ca-certificates.crt is self signed.
2022-03-18T15:38:08.956749Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2022-03-18T15:38:08.984758Z 0 [Warning] [MY-010604] [Repl] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=juju-3eaf1f-1-lxd-2-relay-bin' to avoid this problem.
2022-03-18T15:38:09.154363Z 0 [Warning] [MY-010818] [Server] Error reading GTIDs from relaylog: -1
2022-03-18T15:38:09.200784Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2022-03-18T15:38:09.200883Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.28-0ubuntu0.20.04.3'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu).
2022-03-18T15:38:09.205096Z 2 [Warning] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Automatically adding IPv4 localhost address to the allowlist. It is mandatory that it is added.'
2022-03-18T15:38:09.205130Z 2 [Warning] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Automatically adding IPv6 localhost address to the allowlist. It is mandatory that it is added.'
2022-03-18T15:38:09.235330Z 14 [System] [MY-010597] [Repl] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_applier' executed'. Previous state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''.
2022-03-18T15:38:10.266373Z 2 [System] [MY-011511] [Repl] Plugin group_replication reported: 'This server is working as secondary member with primary member address 172.16.58.45:3306.'
2022-03-18T15:38:11.267447Z 0 [System] [MY-013471] [Repl] Plugin group_replication reported: 'Distributed recovery will transfer data using: Incremental recovery from a group donor'
2022-03-18T15:38:11.267884Z 0 [System] [MY-011503] [Repl] Plugin group_replication reported: 'Group membership changed to 172.16.58.45:3306, 172.16.58.79:3306 on view 16476166099420298:4.'
2022-03-18T15:38:17.370366Z 16 [ERROR] [MY-010596] [Repl] Error reading relay log event for channel 'group_replication_applier': corrupted data in log event
2022-03-18T15:38:17.370430Z 16 [ERROR] [MY-013121] [Repl] Slave SQL for channel 'group_replication_applier': Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, the server was unable to fetch a keyring key required to open an encrypted relay log file, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Error_code: MY-013121
2022-03-18T15:38:17.370480Z 16 [ERROR] [MY-011451] [Repl] Plugin group_replication reported: 'The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.'
2022-03-18T15:38:17.370538Z 14 [ERROR] [MY-011452] [Repl] Plugin group_replication reported: 'Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.'
2022-03-18T15:38:17.370645Z 14 [ERROR] [MY-011712] [Repl] Plugin group_replication reported: 'The server was automatically set into read only mode after an error was detected.'
2022-03-18T15:38:17.370688Z 16 [ERROR] [MY-010586] [Repl] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'FIRST' position 0
2022-03-18T15:38:17.370837Z 56 [ERROR] [MY-011622] [Repl] Plugin group_replication reported: 'Unable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.'
2022-03-18T15:38:17.370908Z 56 [ERROR] [MY-011620] [Repl] Plugin group_replication reported: 'Fatal error during the incremental recovery process of Group Replication. The server will leave the group.'
2022-03-18T15:38:17.370950Z 56 [Warning] [MY-011645] [Repl] Plugin group_replication reported: 'Skipping leave operation: concurrent attempt to leave the group is on-going.'
2022-03-18T15:38:17.370965Z 56 [ERROR] [MY-011712] [Repl] Plugin group_replication reported: 'The server was automatically set into read only mode after an error was detected.'
2022-03-18T15:38:20.447266Z 0 [System] [MY-011504] [Repl] Plugin group_replication reported: 'Group membership changed: This member has left the group.'

unit-mysql-innodb-cluster-1.log /var/log/juju/

2022-03-18 15:46:38 ERROR unit.mysql-innodb-cluster/1.juju-log server.go:327 cluster:6: Cluster is unavailable: Cannot set LC_ALL to locale en_US.UTF-8: No such file or directory
Traceback (most recent call last):
  File "<string>", line 2, in <module>
RuntimeError: Dba.get_cluster: Group replication does not seem to be active in instance '172.16.58.79:3306'


2022-03-18 15:46:38 INFO unit.mysql-innodb-cluster/1.juju-log server.go:327 cluster:6: Remove instance: 172.16.58.63.
2022-03-18 15:46:39 ERROR unit.mysql-innodb-cluster/1.juju-log server.go:327 cluster:6: Failed removing instance 172.16.58.63: Cannot set LC_ALL to locale en_US.UTF-8: No such file or directory
Traceback (most recent call last):
  File "<string>", line 2, in <module>
RuntimeError: Dba.get_cluster: Group replication does not seem to be active in instance '172.16.58.79:3306'


2022-03-18 15:46:39 ERROR unit.mysql-innodb-cluster/1.juju-log server.go:327 cluster:6: Hook error:
Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-mysql-innodb-cluster-1/.venv/lib/python3.8/site-packages/charms/reactive/__init__.py", line 74, in main
    bus.dispatch(restricted=restricted_mode)
  File "/var/lib/juju/agents/unit-mysql-innodb-cluster-1/.venv/lib/python3.8/site-packages/charms/reactive/bus.py", line 390, in dispatch
    _invoke(other_handlers)
  File "/var/lib/juju/agents/unit-mysql-innodb-cluster-1/.venv/lib/python3.8/site-packages/charms/reactive/bus.py", line 359, in _invoke
    handler.invoke()
  File "/var/lib/juju/agents/unit-mysql-innodb-cluster-1/.venv/lib/python3.8/site-packages/charms/reactive/bus.py", line 181, in invoke
    self._action(*args)
  File "/var/lib/juju/agents/unit-mysql-innodb-cluster-1/charm/reactive/mysql_innodb_cluster_handlers.py", line 473, in scale_in
    instance.remove_instance(
  File "/var/lib/juju/agents/unit-mysql-innodb-cluster-1/charm/lib/charm/openstack/mysql_innodb_cluster.py", line 986, in remove_instance
    raise e
  File "/var/lib/juju/agents/unit-mysql-innodb-cluster-1/charm/lib/charm/openstack/mysql_innodb_cluster.py", line 962, in remove_instance
    output = self.run_mysqlsh_script(_script).decode("UTF-8")
  File "/var/lib/juju/agents/unit-mysql-innodb-cluster-1/charm/lib/charm/openstack/mysql_innodb_cluster.py", line 1659, in run_mysqlsh_script
    return subprocess.check_output(cmd, stderr=subprocess.PIPE)
  File "/usr/lib/python3.8/subprocess.py", line 415, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/usr/lib/python3.8/subprocess.py", line 516, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/snap/bin/mysqlsh', '--no-wizard', '--python', '-f', '/root/snap/mysql-shell/common/tmpe2wihrin.py']' returned non-zero exit status 1.

2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60 Traceback (most recent call last):
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60   File "/var/lib/juju/agents/unit-mysql-innodb-cluster-1/charm/hooks/cluster-relation-departed", line 22, in <module>
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60     main()
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60   File "/var/lib/juju/agents/unit-mysql-innodb-cluster-1/.venv/lib/python3.8/site-packages/charms/reactive/__init__.py", line 74, in main
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60     bus.dispatch(restricted=restricted_mode)
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60   File "/var/lib/juju/agents/unit-mysql-innodb-cluster-1/.venv/lib/python3.8/site-packages/charms/reactive/bus.py", line 390, in dispatch
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60     _invoke(other_handlers)
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60   File "/var/lib/juju/agents/unit-mysql-innodb-cluster-1/.venv/lib/python3.8/site-packages/charms/reactive/bus.py", line 359, in _invoke
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60     handler.invoke()
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60   File "/var/lib/juju/agents/unit-mysql-innodb-cluster-1/.venv/lib/python3.8/site-packages/charms/reactive/bus.py", line 181, in invoke
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60     self._action(*args)
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60   File "/var/lib/juju/agents/unit-mysql-innodb-cluster-1/charm/reactive/mysql_innodb_cluster_handlers.py", line 473, in scale_in
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60     instance.remove_instance(
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60   File "/var/lib/juju/agents/unit-mysql-innodb-cluster-1/charm/lib/charm/openstack/mysql_innodb_cluster.py", line 986, in remove_instance
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60     raise e
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60   File "/var/lib/juju/agents/unit-mysql-innodb-cluster-1/charm/lib/charm/openstack/mysql_innodb_cluster.py", line 962, in remove_instance
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60     output = self.run_mysqlsh_script(_script).decode("UTF-8")
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60   File "/var/lib/juju/agents/unit-mysql-innodb-cluster-1/charm/lib/charm/openstack/mysql_innodb_cluster.py", line 1659, in run_mysqlsh_script
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60     return subprocess.check_output(cmd, stderr=subprocess.PIPE)
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60   File "/usr/lib/python3.8/subprocess.py", line 415, in check_output
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60     return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60   File "/usr/lib/python3.8/subprocess.py", line 516, in run
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60     raise CalledProcessError(retcode, process.args,
2022-03-18 15:46:39 WARNING unit.mysql-innodb-cluster/1.cluster-relation-departed logger.go:60 subprocess.CalledProcessError: Command '['/snap/bin/mysqlsh', '--no-wizard', '--python', '-f', '/root/snap/mysql-shell/common/tmpe2wihrin.py']' returned non-zero exit status 1.
2022-03-18 15:46:39 ERROR juju.worker.uniter.operation runhook.go:146 hook "cluster-relation-departed" (via explicit, bespoke hook script) failed: exit status 1
2022-03-18 15:46:39 INFO juju.worker.uniter resolver.go:150 awaiting error resolution for "relation-departed" hook
2022-03-18 15:50:00 INFO juju.worker.uniter resolver.go:150 awaiting error resolution for "relation-departed" hook

Unit in Blocked state /var/log/mysql/error.log

2022-03-18T15:13:02.071901Z 0 [ERROR] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Error on opening a connection to peer node 172.16.58.79:33061 when joining a group. My local port is: 33061.'
2022-03-18T15:13:04.139256Z 0 [Warning] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Reading a request from a remote XCom failed.'
2022-03-18T15:13:04.139458Z 0 [ERROR] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Error connecting to all peers. Member join failed. Local port: 33061'
2022-03-18T15:13:04.200765Z 0 [ERROR] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] The member was unable to join the group. Local port: 33061'
2022-03-18T15:33:34.754358Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user <via user signal>. Shutting down mysqld (Version: 8.0.28-0ubuntu0.20.04.3).
2022-03-18T15:33:35.441600Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.28-0ubuntu0.20.04.3)  (Ubuntu).
2022-03-18T15:38:19.023783Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.28-0ubuntu0.20.04.3) starting as process 462
2022-03-18T15:38:19.040459Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-03-18T15:38:19.412465Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2022-03-18T15:38:19.646417Z 0 [System] [MY-013587] [Repl] Plugin group_replication reported: 'Plugin 'group_replication' is starting.'
2022-03-18T15:38:19.750688Z 0 [Warning] [MY-010068] [Server] CA certificate /etc/ssl/certs/ca-certificates.crt is self signed.
2022-03-18T15:38:19.750744Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2022-03-18T15:38:19.780367Z 0 [Warning] [MY-010604] [Repl] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=juju-3eaf1f-2-lxd-1-relay-bin' to avoid this problem.
2022-03-18T15:38:20.100977Z 0 [Warning] [MY-010818] [Server] Error reading GTIDs from relaylog: -1
2022-03-18T15:38:20.143736Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.28-0ubuntu0.20.04.3'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu).
2022-03-18T15:38:20.144025Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2022-03-18T15:38:20.146809Z 2 [Warning] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Automatically adding IPv4 localhost address to the allowlist. It is mandatory that it is added.'
2022-03-18T15:38:20.146843Z 2 [Warning] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Automatically adding IPv6 localhost address to the allowlist. It is mandatory that it is added.'
2022-03-18T15:38:20.174038Z 11 [System] [MY-010597] [Repl] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_applier' executed'. Previous state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''.
2022-03-18T15:38:27.718171Z 13 [ERROR] [MY-010596] [Repl] Error reading relay log event for channel 'group_replication_applier': corrupted data in log event
2022-03-18T15:38:27.718252Z 13 [ERROR] [MY-013121] [Repl] Slave SQL for channel 'group_replication_applier': Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, the server was unable to fetch a keyring key required to open an encrypted relay log file, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Error_code: MY-013121
2022-03-18T15:38:27.718269Z 13 [ERROR] [MY-011451] [Repl] Plugin group_replication reported: 'The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.'
2022-03-18T15:38:27.718317Z 11 [ERROR] [MY-011452] [Repl] Plugin group_replication reported: 'Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.'
2022-03-18T15:38:27.718402Z 11 [ERROR] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] The member is already leaving or joining a group.'
2022-03-18T15:38:27.718404Z 13 [ERROR] [MY-010586] [Repl] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'FIRST' position 0
2022-03-18T15:38:27.718426Z 11 [ERROR] [MY-011644] [Repl] Plugin group_replication reported: 'Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.'
2022-03-18T15:38:27.718438Z 11 [ERROR] [MY-011712] [Repl] Plugin group_replication reported: 'The server was automatically set into read only mode after an error was detected.'
2022-03-18T15:38:50.293914Z 0 [ERROR] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Timeout while waiting for the group communication engine to be ready!'
2022-03-18T15:38:50.293996Z 0 [ERROR] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] The group communication engine is not ready for the member to join. Local port: 33061'
2022-03-18T15:38:50.354051Z 0 [ERROR] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] The member was unable to join the group. Local port: 33061'
2022-03-18T15:38:55.405878Z 0 [ERROR] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] Error on opening a connection to peer node 172.16.58.79:33061 when joining a group. My local port is: 33061.'
2022-03-18T15:38:55.626226Z 0 [ERROR] [MY-011502] [Repl] Plugin group_replication reported: 'There was a previous plugin error while the member joined the group. The member will now exit the group.'
2022-03-18T15:38:55.626279Z 0 [System] [MY-011503] [Repl] Plugin group_replication reported: 'Group membership changed to 172.16.58.101:3306 on view 16476166099420298:6.'
2022-03-18T15:38:58.700144Z 0 [System] [MY-011504] [Repl] Plugin group_replication reported: 'Group membership changed: This member has left the group.'

Blocked unit some error logs when trying to add the instance /var/log/juju

Traceback (most recent call last):
  File "<string>", line 2, in <module>
mysqlsh.Error: Shell Error (51314): Dba.get_cluster: This function is not available through a session to a standalone instance (metadata exists, instance belongs to that metadata, but GR is not active)

2022-03-18 15:44:07 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 coordinator.DelayedActionCoordinator Publishing state
2022-03-18 15:44:07 INFO juju.worker.uniter.operation runhook.go:152 ran "update-status" hook (via explicit, bespoke hook script)
2022-03-18 15:49:00 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Reactive main running for hook update-status
2022-03-18 15:49:02 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 coordinator.DelayedActionCoordinator Loading state
2022-03-18 15:49:02 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Coordinator: Initializing coordinator layer
2022-03-18 15:49:02 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Initializing Snap Layer
2022-03-18 15:49:02 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Initializing Leadership Layer (is follower)
2022-03-18 15:49:02 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: reactive/layer_openstack.py:64:default_update_status
2022-03-18 15:49:03 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: reactive/layer_openstack.py:82:check_really_is_update_status
2022-03-18 15:49:03 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: reactive/layer_openstack.py:93:run_default_update_status
2022-03-18 15:49:03 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: reactive/mysql_innodb_cluster_handlers.py:132:check_quorum
2022-03-18 15:49:03 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: reactive/mysql_innodb_cluster_handlers.py:234:signal_clustered
2022-03-18 15:49:03 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: reactive/mysql_innodb_cluster_handlers.py:376:request_certificates
2022-03-18 15:49:03 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: hooks/relations/mysql-innodb-cluster/peers.py:69:joined:cluster
2022-03-18 15:49:03 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: hooks/relations/mysql-innodb-cluster/peers.py:75:changed:cluster
2022-03-18 15:49:03 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: hooks/relations/mysql-router/provides.py:47:joined:db-router
2022-03-18 15:49:03 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: hooks/relations/tls-certificates/requires.py:79:joined:certificates
2022-03-18 15:49:33 ERROR unit.mysql-innodb-cluster/2.juju-log server.go:327 Cluster is unavailable: Cannot set LC_ALL to locale en_US.UTF-8: No such file or directory
Traceback (most recent call last):
  File "<string>", line 2, in <module>
mysqlsh.Error: Shell Error (51314): Dba.get_cluster: This function is not available through a session to a standalone instance (metadata exists, instance belongs to that metadata, but GR is not active)

2022-03-18 15:49:33 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 coordinator.DelayedActionCoordinator Publishing state
2022-03-18 15:49:34 INFO juju.worker.uniter.operation runhook.go:152 ran "update-status" hook (via explicit, bespoke hook script)
2022-03-18 15:54:13 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Reactive main running for hook update-status
2022-03-18 15:54:15 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 coordinator.DelayedActionCoordinator Loading state
2022-03-18 15:54:15 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Coordinator: Initializing coordinator layer
2022-03-18 15:54:15 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Initializing Snap Layer
2022-03-18 15:54:15 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Initializing Leadership Layer (is follower)
2022-03-18 15:54:15 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: reactive/layer_openstack.py:64:default_update_status
2022-03-18 15:54:15 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: reactive/layer_openstack.py:82:check_really_is_update_status
2022-03-18 15:54:15 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: reactive/layer_openstack.py:93:run_default_update_status
2022-03-18 15:54:15 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: reactive/mysql_innodb_cluster_handlers.py:132:check_quorum
2022-03-18 15:54:15 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: reactive/mysql_innodb_cluster_handlers.py:234:signal_clustered
2022-03-18 15:54:15 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: reactive/mysql_innodb_cluster_handlers.py:376:request_certificates
2022-03-18 15:54:15 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: hooks/relations/mysql-innodb-cluster/peers.py:69:joined:cluster
2022-03-18 15:54:15 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: hooks/relations/mysql-innodb-cluster/peers.py:75:changed:cluster
2022-03-18 15:54:15 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: hooks/relations/mysql-router/provides.py:47:joined:db-router
2022-03-18 15:54:16 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: hooks/relations/tls-certificates/requires.py:79:joined:certificates
2022-03-18 15:54:46 ERROR unit.mysql-innodb-cluster/2.juju-log server.go:327 Cluster is unavailable: Cannot set LC_ALL to locale en_US.UTF-8: No such file or directory
Traceback (most recent call last):
  File "<string>", line 2, in <module>
mysqlsh.Error: Shell Error (51314): Dba.get_cluster: This function is not available through a session to a standalone instance (metadata exists, instance belongs to that metadata, but GR is not active)

2022-03-18 15:54:46 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 coordinator.DelayedActionCoordinator Publishing state
2022-03-18 15:54:46 INFO juju.worker.uniter.operation runhook.go:152 ran "update-status" hook (via explicit, bespoke hook script)
2022-03-18 15:58:42 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Reactive main running for hook update-status
2022-03-18 15:58:44 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 coordinator.DelayedActionCoordinator Loading state
2022-03-18 15:58:44 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Coordinator: Initializing coordinator layer
2022-03-18 15:58:44 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Initializing Snap Layer
2022-03-18 15:58:44 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Initializing Leadership Layer (is follower)
2022-03-18 15:58:44 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: reactive/layer_openstack.py:64:default_update_status
2022-03-18 15:58:44 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: reactive/layer_openstack.py:82:check_really_is_update_status
2022-03-18 15:58:44 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: reactive/layer_openstack.py:93:run_default_update_status
2022-03-18 15:58:45 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: reactive/mysql_innodb_cluster_handlers.py:132:check_quorum
2022-03-18 15:58:45 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: reactive/mysql_innodb_cluster_handlers.py:234:signal_clustered
2022-03-18 15:58:45 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: reactive/mysql_innodb_cluster_handlers.py:376:request_certificates
2022-03-18 15:58:45 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: hooks/relations/mysql-innodb-cluster/peers.py:69:joined:cluster
2022-03-18 15:58:45 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: hooks/relations/mysql-innodb-cluster/peers.py:75:changed:cluster
2022-03-18 15:58:45 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: hooks/relations/mysql-router/provides.py:47:joined:db-router
2022-03-18 15:58:45 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 Invoking reactive handler: hooks/relations/tls-certificates/requires.py:79:joined:certificates
2022-03-18 15:59:15 ERROR unit.mysql-innodb-cluster/2.juju-log server.go:327 Cluster is unavailable: Cannot set LC_ALL to locale en_US.UTF-8: No such file or directory
Traceback (most recent call last):
  File "<string>", line 2, in <module>
mysqlsh.Error: Shell Error (51314): Dba.get_cluster: This function is not available through a session to a standalone instance (metadata exists, instance belongs to that metadata, but GR is not active)

2022-03-18 15:59:15 INFO unit.mysql-innodb-cluster/2.juju-log server.go:327 coordinator.DelayedActionCoordinator Publishing state
2022-03-18 15:59:16 INFO juju.worker.uniter.operation runhook.go:152 ran "update-status" hook (via explicit, bespoke hook script)

If you need any other logs i will provide them. Also if you know any best practice advices in this case please let me know.

did you solve your problem ? I have a similar one