Comment 5 for bug 1852412

I do believe that there are 2 issues here - (1) is that Juju does not recognised 'locked' machines in MAAS or at least does not know how to handle them; (2) is re-validating credential after machine removal.

I'll keep this report for dealing with credential re-validation since I am not convinced that Juju current behavior re:locked machine issue is not acceptable... With plain remove-machine, Juju reached out to MAAS and MAAS erred out. Running force remove is the only option here (if you really really want the machine gone) since we can only remove Juju reference and not touch the provider instance... Yes, we can also notify the user, i.e. in some way to say "cloud instance still exists, you need to deal with it manually", but besides this additional message, the flow of removal process will not change: you'd still need to go to MAAS to remove offending machine.

So, I'll rename this bug to reflect your difficulties with re-validating a credential since the fact that the machine was locked in MAAS is incidental. I'll add a smaller bug for user message on machine removal.