Comment 2 for bug 1878744

Locally, juju keeps a file called ~/.local/share/juju/models.yaml, which has a list of controllers, the current model for each controller, and other models on that controller.

If you created a model, then removed it, but didn't switch over to another model on that controller, that local file may not have been updated.

I'm going to say that this is legitimately a bug -- that local file shouldn't get out of date. But it won't hurt anything. That dead model isn't sitting in a database somewhere.

I reproduced the issue w/ the following steps on my local lxd cloud:

    juju add-model test-foo localhost
    juju controllers # I see test-foo as the current model
    juju destroy-model test-foo
    juju controllers # I still see test-foo as the current model