kill-controller panic after invalid credential error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Ian Booth |
Bug Description
tvansteenburgh@
Destroying controller "cdk-azure"
Waiting for resources to be reclaimed
Waiting on 2 models, 11 machines, 7 applications
Waiting on 2 models, 11 machines, 7 applications
Waiting on 2 models, 11 machines, 7 applications
Waiting on 2 models, 11 machines, 7 applications
Waiting on 2 models, 11 machines, 7 applications
Waiting on 2 models, 11 machines, 7 applications
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 4m29s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 4m24s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 4m18s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 4m13s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 4m8s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 4m3s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 3m58s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 3m53s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 3m47s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 3m42s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 3m37s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 3m32s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 3m27s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 3m22s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 3m17s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 3m11s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 3m6s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 3m1s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 2m56s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 2m51s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 2m46s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 2m41s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 2m35s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 2m30s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 2m25s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 2m20s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 2m15s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 2m10s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 2m4s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 1m59s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 1m54s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 1m49s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 1m44s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 1m39s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 1m34s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 1m28s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 1m23s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 1m18s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 1m13s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 1m8s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 1m3s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 57s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 52s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 47s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 42s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 37s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 32s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 27s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 21s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 16s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 11s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 6s
Waiting on 2 models, 11 machines, 7 applications, will kill machines directly in 1s
Killing admin/cdk-azure directly
ERROR deleting resource group "juju-cdk-
Killing admin/default directly
ERROR deleting resource group "juju-default-
ERROR there were problems destroying some models, manual intervention may be necessary to ensure resources are released
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1b8678d]
goroutine 1 [running]:
github.
github.
github.
github.
github.
github.
github.
github.
github.
github.
github.
github.
github.
github.
main.main()
Changed in juju: | |
milestone: | none → 2.8-rc1 |
assignee: | nobody → Ian Booth (wallyworld) |
status: | New → In Progress |
importance: | Undecided → High |
summary: |
- Azure kill-controller panic + kill-controller panic after invalid credential error |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Client: 2.7.6-bionic-amd64
Controller: 2.5.4