Verification of proper model destroy in Azure

[Rick Harding]

It's a timing thing. I bootstrapped with b11 on azure and will here's my
shell history:

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

Note that after destroy the model was still around, I could switch of/to
it, and it showed in the model list. It was somewhere in there were it
finally went away. My attempt at debug-log hung so I ctrl-c'd and then
after that, while still on the model that should be gone, I got the error
that Mark did.

Let me know if you want to pull this into the bug or you'd like me to add
to it in any way.

On Fri, Jul 15, 2016 at 9:13 PM Alexis Bruemmer <
alexis.bruemmer at canonical.com> wrote:

> *If* someone is in azure already can they please verify that they can
> destroy a model and get this message when running "juju status" in the
> destroyed model:
>
> "juju status
> ERROR no model in focus
>
> Please use "juju models" to see models available to you.
> You can set current model by running "juju switch"
> or specify any other model on the command line using the "-m" flag."
>
> see https://bugs.launchpad.net/juju-core/+bug/1602034 for background.
> The code path mark hit is not in beta12 anymore (thank you roger!)  but I
> dont want to push back until we verified in azure.
>
>
> --
> Alexis Bruemmer
> Juju Core Manager, Canonical Ltd.
> (503) 686-5018
> alexis.bruemmer at canonical.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20160716/0d320747/attachment.html>