Comment 5 for bug 1505504

+1 ty andrew

On Wed, May 25, 2016 at 12:01 AM Andrew Wilkins <
<email address hidden>> wrote:

> We've been clearing the current model for a while now, but we've still
> been printing out an ugly/invalid error message that states there's no
> current controller. I've got a PR that will change this to correctly
> state that there's no current model, and how you can go about setting
> one.
>
> $ juju status
> ERROR no model specified
>
> There is no current model specified for the current controller,
> and none specified on the command line. Please use "juju switch"
> to set the current model, or specify a model on the command line
> using the "-m" flag.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1505504
>
> Title:
> destroying the current model should clear the current-model
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1505504/+subscriptions
>