Comment 6 for bug 1646385

On 2019-06-07, we encountered this when working on a customer's cloud, trying to add a new mysql unit to replace one which had failed. We got the same "inconsistent state" issues, and we were able to force it to go through by just continuing to retry. This was with juju client 2.6.3-trusty-amd64, juju model at 2.4.3.

That environment has since been upgraded, so I can't readily re-test this; just wanted to provide a data point that this issue might still be persisting to some degree.