[22:46] <bladernr_> Hey, anyone around with ideas on how to destroy a unit in agent state down that failed to deploy in ec2?
[22:46] <bladernr_> via juju :)
[22:47] <marcoceppi> bladernr_: the agent-state is down?
[22:48] <bladernr_> marcoceppi: yep...
[22:48] <bladernr_> http://pastebin.ubuntu.com/6273454/
[22:48] <jcastro> kurt__, around?
[22:48] <bladernr_> what happened is I did a juju-deploy quantum-gateway.  The instance started to spin up in ec2 but failed to completely start
[22:48] <bladernr_> so now I have no way to access the node, and juju won't actually destroy it since it's agent-state is down.
[22:48] <bladernr_> :(
[22:49] <marcoceppi> bladernr_: if agent-state is down then it'll be hard to communicate with the node. What you can try to do is run `juju resolved quantum-gateway/0` a few times, to see if that moves this process along
[22:49] <bladernr_> already tried :( I was hoping for a way to just tell juju to forget about that unit and machine manually
[22:50] <bladernr_> juju should have a --force option to forcibly remove things
[22:50] <bladernr_> IMO
[22:50] <marcoceppi> bladernr_: there's probably a bug on that, let me check
[22:51] <bladernr_> thanks… I tried looking but my search-fu is weak
[22:53] <marcoceppi> bladernr_: https://bugs.launchpad.net/juju-core/+bug/1089289
[22:53] <_mup_> Bug #1089289: destroy-unit --force <destroy-unit> <doc> <juju-core:Triaged> <https://launchpad.net/bugs/1089289>
[22:54] <bladernr_> marcoceppi: you are awesome :)
[22:56] <bladernr_> subscribed and commented on.  Thanks for finding that :)
[23:06] <marcoceppi> bladernr_: np! Thanks for the update, it'll help to show more and more people encountering this issue