Default model automatically changed to the controller's

[Haw Loeung]

Hi,

Since upgrading our main Juju 2 controller to 2.4.3 (was 2.3.9 or so), it seems every now and again the default model switches to the Juju 2.x controller. For example:

| (mojo-prod-community-ubuntu-com)prod-community-ubuntu-com@host:~$ jsft
| ERROR current model for controller prodstack-is not found

| (mojo-prod-community-ubuntu-com)prod-community-ubuntu-com@host:~$ juju models
| Controller: prodstack-is

| Model Cloud/Region Status Machines Cores Access | Last connection
| admin/prod-community-ubuntu-com prodstack-45/bootstack-ps45 available 4 10 admin 15 hours ago

Switching with the following fixes this, until the next time it changes/reverts back.

| juju switch admin/prod-community-ubuntu-com

[Haw Loeung (hloeung)]

Ah, for some reason, ~/.local/share/juju was rewritten as follows:

| controllers:
| prodstack-is: {}

[Haw Loeung (hloeung)]

err, that's ~/.local/share/juju/models.yaml

[Junien F (axino)]

Needless to say, our juju client also got upgraded to 2.4.3, and this is likely where the problem is.

[Haw Loeung (hloeung)]

Looks like Jacek had already filed a bug about this - LP:1796148