Cannot remove-machine or destroy-model on OpenStack cloud when machine is down
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Incomplete
|
Low
|
Unassigned | ||
2.6 |
Fix Released
|
High
|
Unassigned |
Bug Description
Using Juju 2.5 client/controller, we've created several models against an OpenStack cloud, however, the machines within those models haven't provisioned because we have run out of resources within OpenStack.
This leaves juju status in the following state:
ubuntu@
Model Controller Cloud/Region Version SLA Timestamp Notes
wavvkqkykaly juju_main dpcop/RegionOne 2.5.0 unsupported 14:07:30Z attempt 9 to destroy model failed (will retry): model not empty, found 1 machine, 2 applications (model not empty)
App Version Status Scale Charm Store Rev OS Notes
etcd waiting 0/1 etcd jujucharms 319 ubuntu
kubernetes-master waiting 0/1 kubernetes-master jujucharms 542 ubuntu exposed
Unit Workload Agent Machine Public address Ports Message
etcd/0 waiting allocating 0 waiting for machine
kubernetes-master/0 waiting allocating 0 waiting for machine
Machine State DNS Inst id Series AZ Message
0 down pending bionic cannot run instance: with fault "Exceeded maximum number of retries. Exhausted all hosts available for retrying build failures for instance d4e0e6ed-
In this state, it appears impossible to remove the machine (even with --force) or the model.
ubuntu@
14:09:54 INFO juju.cmd supercommand.go:57 running juju [2.5.0 gc go1.10.4]
14:09:54 DEBUG juju.cmd supercommand.go:58 args: []string{
14:09:54 INFO juju.juju api.go:67 connecting to API addresses: [172.16.20.50:17070 10.5.1.3:17070 252.3.0.1:17070]
14:09:54 DEBUG juju.api apiclient.go:883 successfully dialed "wss://
14:09:54 INFO juju.api apiclient.go:603 connection established to "wss://
14:09:54 INFO cmd remove.go:185 removing machine 0
14:09:54 INFO cmd remove.go:193 - will remove unit etcd/0
14:09:54 INFO cmd remove.go:193 - will remove unit kubernetes-master/0
14:09:54 DEBUG juju.api monitor.go:35 RPC connection died
14:09:54 INFO cmd supercommand.go:502 command finished
however, the machine remains in the model.
tags: | added: atos |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.6-beta1 |
tags: | added: teardown |
Changed in juju: | |
milestone: | 2.6-beta1 → 2.6-beta2 |
Changed in juju: | |
milestone: | 2.6-beta2 → 2.6-rc1 |
Changed in juju: | |
milestone: | 2.6-rc1 → 2.6-rc2 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
@Ed Stewart (emcs2),
Do you have controller and/or machine/unit logs? I think I know what's going on but I'd like to see what you got.