departing relation fails on leader if removed instance is already down.
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL InnoDB Cluster Charm | Status tracked in Trunk | |||||
Jammy |
Triaged
|
High
|
Unassigned | |||
Trunk |
In Progress
|
High
|
Unassigned |
Bug Description
Traceback is:
unit-mysql-
unit-mysql-
such file or directory
NOTE: MySQL Error 2003 (HY000): Can't connect to MySQL server on '172.20.0.36' (113)
ERROR: The instance 172.20.0.36:3306 is not reachable and does not belong to the cluster either. Please ensure the member is either connectable or remove it through the exact
address as shown in the cluster status output.
Traceback (most recent call last):
File "<string>", line 3, in <module>
mysqlsh.Error: Shell Error (51104): Cluster.
unit-mysql-
Traceback (most recent call last):
File "/var/lib/
bus.
File "/var/lib/
_invoke(
File "/var/lib/
handler.
File "/var/lib/
self.
File "/var/lib/
instance.
File "/var/lib/
raise e
File "/var/lib/
output = self.run_
File "/var/lib/
return subprocess.
File "/usr/lib/
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/
raise CalledProcessEr
subprocess.
1.
Need to trap the error in "remove_instance()" and propagate the failure to the action, but just handle it gracefully for the departing relation handler.
Fix proposed to branch: master /review. opendev. org/c/openstack /charm- mysql-innodb- cluster/ +/885130
Review: https:/