Juju Node stuck in "life: dying" after trying to destroy-service
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-
2013-09-10 21:49:18 INFO juju.state open.go:68 opening state; mongo addresses: ["3nafd.
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-
charm: cs:precise/
exposed: false
life: dying
relations:
cluster:
- nova-cloud-
units:
nova-
So now I will likely have to destroy all services to fix this and start over.