Ghost models exist after being destroyed

[Anastasia]

[public bug, moved from github]
Models appear to persist after being destroyed.

JuJu: 2.0-beta8-xenial-amd64
Series: Xenial
Localhost on LXD

wurde@solace:~/GitLab/charm-netdata$ juju list-models
MODEL OWNER STATUS LAST CONNECTION
admin admin@local available 3 hours ago
devenv admin@local destroying 3 hours ago
default* admin@local available 18 minutes ago
devenv1 admin@local destroying 18 minutes ago

I even went in and removed the containers using the lxc delete command manually and same result.

[Redjouir (redjouir-deactivatedaccount)]

I can still switch to these models stuck in "destroying" state. When I do a `juju status` I see that there are no services or units. However there are machines in a pending STATE and with pending INS-ID.

Something about the model teardown requires the machines. And I don't know what command exists to "flush" the juju controller state. I should be able to point to a model and say destroy-model and it be destroyed regardless of wither the agent can access it.

[Andrew Wilkins (axwalk)]

What's your expectation here? Like just about everything else in Juju, model destruction is asynchronous. The "undertaker" worker will destroy the model, and when it's done it'll be removed from the list.

[Adam Stokes (adam-stokes)]

So juju list-models shows us it is in a destroying state, couldn't we use that status to not allow someone to switch to that model?

[Cheryl Jennings (cherylj)]

I'd argue that this bug is a use case for being able to switch to a model in a destroying state. It would be helpful to see a status output from the model that isn't being destroyed to understand the state of it.

[Cheryl Jennings (cherylj)]

It would be helpful to understand why the model wasn't able to complete destruction. If you can recreate, can you attach the output of status for the model, and machine-0.log from the controller?

[Anastasia (anastasia-macmood)]

Marking this as duplicate as the other bug contains logs.