destroy-machine --force
Bug #1089291 reported by
William Reade
This bug affects 15 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
William Reade | ||
| 1.16 |
Fix Released
|
Critical
|
William Reade | ||
| juju-core (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Saucy |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
[Impact]
Unresponsive machines cannot be removed/destroyed, consuming resourcs.
[Test Case]
This of course requires a unresponsive machine; however this can be simulated by destroying a machine that is still installing.
juju destroy-machine <machineid> # will fail
juju destroy-machine --force <machineid> # will succeed
[Regression potential]
Part of the upstream tested 1.16.6 point release.
[Original bug report]
Unresponsive machine agents may require that we forcibly set the machine to Dead to allow the provisioning agent to release its instance.
see also lp:1089289
Related branches
lp://staging/~fwereade/juju-core/api-force-destroy-machines
- Juju Engineering: Pending requested
-
Diff: 1119 lines (+369/-287)17 files modifiedcmd/juju/destroymachine.go (+18/-1)
cmd/juju/destroymachine_test.go (+51/-14)
cmd/juju/destroyunit.go (+1/-1)
cmd/jujud/machine_test.go (+1/-1)
state/api/client.go (+7/-1)
state/api/params/params.go (+1/-0)
state/apiserver/client/client.go (+52/-2)
state/apiserver/client/client_test.go (+136/-31)
state/apiserver/client/perm_test.go (+1/-1)
state/cleanup_test.go (+26/-8)
state/life.go (+8/-1)
state/life_test.go (+5/-15)
state/machine.go (+20/-3)
state/machine_test.go (+13/-44)
state/service_test.go (+3/-3)
state/state.go (+0/-67)
state/unit_test.go (+26/-94)
Revision history for this message
| William Reade (fwereade) wrote | #1 |
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
Revision history for this message
| William Reade (fwereade) wrote | #2 |
| Changed in juju-core: | |
| importance: | Low → High |
| Changed in juju-core: | |
| milestone: | none → 1.16.0 |
| summary: |
- terminate-machine --force + destroy-machine --force |
Revision history for this message
| Mark Ramm (mark-ramm) wrote | #3 |
| Changed in juju-core: | |
| milestone: | 1.16.0 → 2.0 |
| tags: | added: canonical-webops |
| tags: | added: destroy-machine |
| tags: | added: theme-oil |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #4 |
| Changed in juju-core: | |
| importance: | High → Critical |
| milestone: | 2.0 → 1.17.0 |
| Changed in juju-core: | |
| assignee: | nobody → William Reade (fwereade) |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| milestone: | 1.17.0 → 2.0 |
| Changed in juju-core: | |
| milestone: | 2.0 → 1.17.0 |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| John A Meinel (jameinel) wrote | #5 |
Revision history for this message
| Kapil Thangavelu (hazmat) wrote | #6 |
Revision history for this message
| Kapil Thangavelu (hazmat) wrote | #7 |
Revision history for this message
| John A Meinel (jameinel) wrote | #8 |
Revision history for this message
| John A Meinel (jameinel) wrote | #9 |
| Changed in juju-core: | |
| importance: | Critical → High |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
| Changed in juju-core (Ubuntu): | |
| status: | New → Fix Released |
| description: | updated |
Revision history for this message
| Rolf Leggewie (r0lf) wrote | #11 |
| Changed in juju-core (Ubuntu Saucy): | |
| status: | New → Won't Fix |
To post a comment you must log in.
I consider this low priority until we have the unit story sorted out cleanly.