Comment 3 for bug 1602034

I played with this and can get the b11 message if I destroy the model, switch to another model, and switch back to the dying model. In Azure it was taking > 60s for that model to disappear. In the meantime I could run juju status on the dying model and get an empty status output.

Once the model finally went away I'd get the

 ERROR connecting with bootstrap config: aborted

message.

I upgraded to beta12 to see what would happen and experienced a different message but the same behavior. In beta12 you get

juju status
ERROR unknown model: "55459f0f-56c8-4f0b-8cf7-b8a1042df2aa" (not found)

A sample output for steps to reproduce from b11, b12 is the same with only the error message in the end being different.

https://pastebin.canonical.com/161089/