Juju controllers should show correct active controller

[Haw Loeung]

Hi,

As Ian has pointed out, 'juju controllers' uses the local cached yaml to determine the active controller instead of the real one. E.g.

| $ export JUJU_CONTROLLER=prodstack-is-2
| ...
| prodstack-is* controller admin superuser prodstack-45/bootstack-ps45 227 878 3 2.5.0
| prodstack-is-2 controller admin superuser prodstack-45/bootstack-ps45 4 3 3 2.5-rc1.1

This is confusing and should be fixed.

Thanks,

Haw

[Anastasia (anastasia-macmood)]

The same behavior can be observed with JUJU_MODEL and models related commands.

They should be fixed as well.

[Anastasia (anastasia-macmood)]

I have fixed this behavior in https://github.com/juju/juju/pull/9778, heading into 2.5.2.

We have had some commands behaving inconsistently and *forgetting* that current controller can be set by either $JUJU_CONTROLLER or $$JUJU_MODEL environment variables.

[John A Meinel (jameinel)]

https://github.com/juju/juju/pull/9819 merges 9778 into develop