Instances removed using 'remove-instance' action throw failure message with a blocked state
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL InnoDB Cluster Charm |
New
|
Undecided
|
Unassigned |
Bug Description
If an instance is removed from the MySQL cluster using 'juju run-action remove-instance', the action throws back a failed response and the instance/unit results in a blocked state.
buntu@ahmadfsbd
Action queued with id: "2"
ubuntu@
UnitId: mysql-innodb-
id: "2"
status: running
timing:
enqueued: 2022-07-25 14:39:18 +0000 UTC
started: 2022-07-25 14:39:18 +0000 UTC
ubuntu@
UnitId: mysql-innodb-
id: "2"
message: Remove instance failed
results:
output: "Cannot set LC_ALL to locale en_US.UTF-8: No such file or directory\nThe
instance will be removed from the InnoDB cluster. Depending on the instance\nbeing
the Seed or not, the Metadata session might become invalid. If so, please\nstart
a new session to the Metadata Storage R/W instance.
is attempting to leave the cluster.
failed to leave the cluster: Variable 'group_
persistent variable\nTraceback (most recent call last):\n File \"<string>\",
line 3, in <module>
Variable 'group_
traceback: |
Traceback (most recent call last):
File "/var/lib/
output = 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.
status: failed
timing:
completed: 2022-07-25 14:39:26 +0000 UTC
enqueued: 2022-07-25 14:39:18 +0000 UTC
started: 2022-07-25 14:39:18 +0000 UTC
ubuntu@
mysql-innodb-
er is ONLINE and can tolerate up to ONE failure. 1 member is not active.
mysql-innodb-
er is ONLINE and can tolerate up to ONE failure. 1 member is not active.
mysql-innodb-
er is ONLINE and can tolerate up to ONE failure. 1 member is not active.
mysql-innodb-
is instance. Please check logs for details.
The 'juju debug' shows the following error on the subject instances:
unit-mysql-
Trying to add the instance back to the cluster using 'juju run-action rejoin-instance' shows a success response, however, the instance stays in a blocked state:
ubuntu@
Action queued with id: "4"
ubuntu@
UnitId: mysql-innodb-
id: "4"
results:
outcome: Success
output: ""
status: completed
timing:
completed: 2022-07-25 14:52:32 +0000 UTC
enqueued: 2022-07-25 14:52:23 +0000 UTC
started: 2022-07-25 14:52:23 +0000 UTC
Deployed Using Master Branch: https:/
Channel: 8.0/stable
description: | updated |