juju status returns ERROR not logged in

[Matt Bruzek]

While using juju for testing and I encountered a situation where I am "not logged in" and when trying to log in that fails.

ubuntu@devbox:~$ juju status
ERROR not logged in

Please use "juju controllers" to view all controllers available to you.
You can login into an existing controller using "juju login -c <controller>".

ubuntu@devbox:~$ juju login -c amazon
username: mbruzek
ERROR already logged in

Run "juju logout" first before attempting to log in as a different user.

ubuntu@devbox:~$ juju status
ERROR not logged in

Please use "juju controllers" to view all controllers available to you.
You can login into an existing controller using "juju login -c <controller>".

ubuntu@devbox:~$ juju controllers
CONTROLLER MODEL USER CLOUD/REGION
amazon default admin@local aws/us-west-1

I arrived at this situation using the following steps:

juju bootstrap amazon aws/us-west-1
juju bootstrap google google/us-central1
juju destroy-controller -y google --destroy-all-models

Juju seems to have lost context and the error message has nothing to do with the actual problem.

As it turns out a `juju switch amazon` solved my problem. While destroying controller can Juju switch to the other available controllers? Or at least present a better error message?

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.