Juju Node stuck in "life: dying" after trying to destroy-service

Bug #1223573 reported by Kurt
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
juju-core
New
Undecided
Unassigned

Bug Description

Here is the use case to reproduce:

After doing something bad to my node w/r IP addressing, I completely blew up my node after trying to reboot. I had no ssh access to fix anything.

I could:
destroy the service from the gui (which showed icon disappear but service was still there)
destroy the service from the CLI (which gave no error condition return)

I could not:
Fully destroy the service. Juju believes there is still a running system there.

kurt@maas-cntrl:~$ juju -vvv destroy-service nova-cloud-controller
2013-09-10 21:49:18 INFO juju.state open.go:68 opening state; mongo addresses: ["3nafd.master:37017"]; entity ""
2013-09-10 21:49:18 INFO juju.state open.go:106 connection established
2013-09-10 21:49:18 INFO juju supercommand.go:284 command finished

juju-status for the controller:

  nova-cloud-controller:
    charm: cs:precise/nova-cloud-controller-14
    exposed: false
    life: dying
    relations:
      cluster:
      - nova-cloud-controller
    units:
      nova-cloud-controller/0:
        agent-state: down
        agent-state-info: (started)
        agent-version: 1.12.0

So now I will likely have to destroy all services to fix this and start over.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.