kill-controller broken for CAAS

Bug #1904971 reported by Yang Kelvin Liu
12
This bug affects 1 person
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 d0debe929e850349bf016658fa2a2b6b91987f24 gc go1.14.12]
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.183.24:17070]
14:15:26 INFO cmd kill.go:119 Unable to open API: open connection timed out
14:15:26 DEBUG juju.kubernetes.provider provider.go:121 opening model "controller".
ERROR getting controller environ: getting environ using bootstrap config from client store: unable to determine legacy status for namespace controller: Get "https://172.16.104.2:16443/api/v1/namespaces/controller": dial tcp 172.16.104.2:16443: connect: connection refused
14:15:26 DEBUG cmd supercommand.go:537 error stack:
Get "https://172.16.104.2:16443/api/v1/namespaces/controller": dial tcp 172.16.104.2:16443: connect: connection refused
github.com/juju/juju/caas/kubernetes/provider/utils/labels.go:49: unable to determine legacy status for namespace controller
github.com/juju/juju/caas/kubernetes/provider/k8s.go:186:
github.com/juju/juju/cmd/juju/controller/destroy.go:548: getting environ using bootstrap config from client store
github.com/juju/juju/cmd/juju/controller/kill.go:125: getting controller environ
$ 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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.