Comment 6 for bug 1190715
Revision history for this message
| William Reade (fwereade) wrote Re: Unit in error, yet juju resolved claims it's fixed | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
...oh, hell, I had mixed state with another bug in my mind. To restate:
1) Tools for dealing with unexpectedly missing instances are on their way (--force), but at the moment we just trust that the user won't sabotage their own system. So please don't terminate instances out of band.
2) If a unit's never been run, service destroy should definitely short-circuit, so we don't need to wait for the unit agents to kill themselves.
3) In the meantime, manually destroying the units will induce the shortcut anyway, so there's a workaround for the cases that don't involve --force.
4) (inferred) What you'd *really* like is to be able to `juju destroy-machine 1` and have all its units automatically destroyed. If that's correct, I think it's a distinct bug...
I'm renaming the bug in light of (2).