Comment 3 for bug 1900789

Have you done a remove-machine --force? The normal destroy model should be
shutting things down cleanly, but 'remove-machine --force' should delete
the machine not waiting for units, etc to clean up.

On Mon, Oct 26, 2020 at 9:35 PM Haw Loeung <email address hidden>
wrote:

> Controllers originally deployed/provisioned with 2.8.1. Upgraded
> recently to 2.8.3 (Sept 30th). Model itself was also deployed 2.8.1 and
> upgraded to 2.8.3.
>
> Originally used remove-unit to spin up a new one. This was because the
> unit it self failed to boot due to the grub calloc bug, LP:1889556, I
> think this is the important and missing piece here. So the unit is left
> in an unbootable state and juju is unable to properly / fully? remove
> it?
>
> The storage doesn't exist though:
>
> | $ juju list-storage
> | Unit Storage id Type Pool
> Size Status Message
> | ubuntu-repository-cache/0 ubuntu-repository-cache/0 filesystem azure
> 100GiB attached
> | ubuntu-repository-cache/2 ubuntu-repository-cache/2 filesystem azure
> 100GiB attached
>
>
> ** Changed in: juju
> Status: Incomplete => New
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1900789
>
> Title:
> Azure provider: Can't remove machine (with storage)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1900789/+subscriptions
>