destroy-machine --force

Bug #1089291 reported by William Reade on 2012-12-12
This bug affects 15 people
Affects Status Importance Assigned to Milestone
William Reade
William Reade
juju-core (Ubuntu)

Bug Description

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

William Reade (fwereade) wrote :

I consider this low priority until we have the unit story sorted out cleanly.

Changed in juju-core:
status: New → Triaged
importance: Undecided → Low
William Reade (fwereade) wrote :

...but still, actually, high priority; just that it should be done after the unit is, because a replacement for a zombie machine generally cannot act usefully without replacements for its assigned zombie units in play.

See also lp:1190715

Changed in juju-core:
importance: Low → High
Mark Ramm (mark-ramm) on 2013-09-26
Changed in juju-core:
milestone: none → 1.16.0
William Reade (fwereade) on 2013-09-28
summary: - terminate-machine --force
+ destroy-machine --force
Mark Ramm (mark-ramm) wrote :

Is this related to the bug kapil filed?

Mark Ramm (mark-ramm) on 2013-10-03
Changed in juju-core:
milestone: 1.16.0 → 2.0
Curtis Hovey (sinzui) on 2013-10-11
tags: added: canonical-webops
Curtis Hovey (sinzui) on 2013-10-12
tags: added: destroy-machine
Curtis Hovey (sinzui) on 2013-10-14
tags: added: theme-oil
Curtis Hovey (sinzui) wrote :

See bug 1233457 about a cases where the state-server failed to handle a cases where a dying agent's machine terminated before the state server cold tell it that it was dead.

Mark Ramm (mark-ramm) on 2013-11-08
Changed in juju-core:
importance: High → Critical
milestone: 2.0 → 1.17.0
Tim Penhey (thumper) on 2013-11-11
Changed in juju-core:
assignee: nobody → William Reade (fwereade)
status: Triaged → In Progress
William Reade (fwereade) on 2013-11-11
Changed in juju-core:
milestone: 1.17.0 → 2.0
Curtis Hovey (sinzui) on 2013-11-12
Changed in juju-core:
milestone: 2.0 → 1.17.0
William Reade (fwereade) on 2013-11-13
Changed in juju-core:
status: In Progress → Fix Committed
John A Meinel (jameinel) wrote :

This is something we'd like to consider backporting to the 1.16 series. We may decide not to, but we don't want to forget about it.

Kapil Thangavelu (hazmat) wrote :

so for folks on 1.16.3 i've had put together a script that does the direct db deletion. it should only be considered after db introspection as its specifically around the scenario of a machine with no units, stuck in dying. it comes with no warranty, if you need to use it please ping me on irc before hand.

Kapil Thangavelu (hazmat) wrote :

Script to dump db for for foresenic analysis, used to verify db structure before use of machine removal script.

John A Meinel (jameinel) wrote :

The changes for this got bumped off to the side in my lp:~jameinel/juju-core/preparation-for-1.16.5
So I'm retargetting this for 1.16.5.

John A Meinel (jameinel) wrote :

The changes were landed back into the 1.16 series.

Curtis Hovey (sinzui) on 2013-12-13
Changed in juju-core:
importance: Critical → High
Curtis Hovey (sinzui) on 2013-12-20
Changed in juju-core:
status: Fix Committed → Fix Released
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:

tags: added: iso-testing
James Page (james-page) on 2014-02-07
Changed in juju-core (Ubuntu):
status: New → Fix Released
James Page (james-page) on 2014-03-25
description: updated
Rolf Leggewie (r0lf) wrote :

saucy has seen the end of its life and is no longer receiving any updates. Marking the saucy task for this ticket as "Won't Fix".

Changed in juju-core (Ubuntu Saucy):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers