Machine stuck in juju status if the machine doesn't start

Bug #1236598 reported by David Lawson on 2013-10-07
This bug report is a duplicate of:  Bug #1089291: destroy-machine --force. Edit Remove
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Undecided
Unassigned
pyjuju
Undecided
Unassigned

Bug Description

If a machine fails to provision cleanly that machine is stuck in juju status permanently, even if the underlying nova instance has been deleted. This results in juju status output such as:
  "24":
    agent-state: pending
    instance-id: f8784048-6dfe-4f65-b717-8c216cb585d3
    instance-state: missing
    life: dying
    series: precise
    hardware: arch=amd64 cpu-cores=2 mem=1024M root-disk=51200M

Running juju destroy-machine for that machine returns without errors, but also doesn't remove the machine. Is there a way to remove these from juju status and/or should they eventually expire?

David Lawson (deej) on 2013-10-07
tags: added: canonical-webops-juju
Curtis Hovey (sinzui) on 2013-10-11
tags: added: canonical-webops
removed: canonical-webops-juju
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers