kill-controller broken for CAAS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Unassigned |
Bug Description
$ juju kill-controller -t 0 -y k1 --debug
14:15:16 INFO juju.cmd supercommand.go:56 running juju [2.9-rc3 0 d0debe929e85034
14:15:16 DEBUG juju.cmd supercommand.go:57 args: []string{"juju", "kill-controller", "-t", "0", "-y", "k1", "--debug"}
14:15:16 INFO juju.juju api.go:76 connecting to API addresses: [10.152.
14:15:26 INFO cmd kill.go:119 Unable to open API: open connection timed out
14:15:26 DEBUG juju.kubernetes
ERROR getting controller environ: getting environ using bootstrap config from client store: unable to determine legacy status for namespace controller: Get "https:/
14:15:26 DEBUG cmd supercommand.go:537 error stack:
Get "https:/
github.
github.
github.
github.
$ juju controllers
Use --refresh option with this command to see the latest information.
Controller Model User Access Cloud/Region Models Nodes HA Version
k1* controller admin superuser microk8s/localhost 1 1 - 2.9-rc3
broker.Destroy handles this inaccessible cluster error but the IsLegacyModelLabels was called before we reach here, then Juju errors out and prevents the controller gets killed.
Changed in juju: | |
importance: | Undecided → High |
status: | New → Triaged |
milestone: | none → 2.8-next |