Comment 8 for bug 1954306

I disagree this is an "Invalid" bug. Surely it is not a charm bug, since any instance attempted to be removed manually results in the same error, but this is happening in every single cluster deployed by the charm, no exceptions, and it leaves the instance in an error state, requiring cleanup. I believe the charm is configuring the cluster in a way that sets up the conditions for the problem to happen. I have a hard time finding the same scenario described anywhere on the Internet, except when deployed by the charm.