ERROR getting controller environ: unable to get bootstrap information from client store or API

[Ryan Beisner]

Kill controller fails when the controller instance is gone, leaving the user to manually clean up controllers.yaml.

#### Juju belives a controller exists, but it does not:

jenkins@juju-001b34-osci-18:~$ juju controllers
Use --refresh option with this command to see the latest information.

Controller Model User Access Cloud/Region Models Nodes HA Version
auto-osci-sv07* controller admin superuser serverstack/serverstack 3 1 none 2.6.9

...

#### Cannot destroy or kill the controller:

jenkins@juju-001b34-osci-18:~$ juju kill-controller auto-osci-sv07
WARNING! This command will destroy the "auto-osci-sv07" controller.
This includes all machines, applications, data and other resources.

Continue? (y/N):y
Unable to open API: open connection timed out
ERROR getting controller environ: unable to get bootstrap information from client store or API

...

#### Just move the yaml, and all is well:

jenkins@juju-001b34-osci-18:~/.local/share/juju$ mv controllers.yaml controllers.yaml.old

jenkins@juju-001b34-osci-18:~/.local/share/juju$ juju controllers
ERROR No controllers registered.

Please either create a new controller using "juju bootstrap" or connect to
another controller that you have been given access to using "juju register".

...

#### Version info:

channels:
  stable: 2.6.9 2019-09-25 (9102) 68MB classic
  candidate: ↑
  beta: ↑
  edge: 2.7-beta1+develop-c449d0e 2019-09-30 (9128) 75MB classic
  2.6/stable: 2.6.9 2019-09-26 (9102) 68MB classic
  2.6/candidate: ↑
  2.6/beta: ↑
  2.6/edge: 2.6.9+2.6-f190cd8 2019-09-20 (9083) 74MB classic
  2.5/stable: 2.5.8 2019-06-27 (8361) 67MB classic
  2.5/candidate: ↑
  2.5/beta: ↑
  2.5/edge: 2.5.9+2.5-36af233 2019-07-24 (8546) 73MB classic
  2.4/stable: 2.4.7 2019-05-23 (6012) 58MB classic
  2.4/candidate: ↑
  2.4/beta: ↑
  2.4/edge: ↑
  2.3/stable: 2.3.9 2018-09-19 (5267) 55MB classic
  2.3/candidate: ↑
  2.3/beta: ↑
  2.3/edge: 2.3.10+2.3-41313d1 2019-03-25 (7080) 55MB classic
installed: 2.6.9 (9102) 68MB classic

jenkins@juju-001b34-osci-18:~$ juju --version
2.6.9-xenial-amd64

[Ryan Beisner (1chb1n)]

When we see this condition, `juju controllers --refresh` is not helpful because it doesn't refresh:

jenkins@juju-001b34-osci-18:~$ time juju controllers --refresh --debug
16:41:25 INFO juju.cmd supercommand.go:57 running juju [2.6.9 gc go1.10.4]
16:41:25 DEBUG juju.cmd supercommand.go:58 args: []string{"/snap/juju/9102/bin/juju", "controllers", "--refresh", "--debug"}
16:41:25 INFO juju.juju api.go:67 connecting to API addresses: [172.17.107.3:17070 252.3.0.1:17070]

^C

real 3m15.526s
user 0m0.152s
sys 0m0.148s

[Tim Penhey (thumper)]

If the controller has gone, use `juju unregister` to remove the controller entry.

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

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