Comment 4 for bug 1190715
Revision history for this message
| William Reade (fwereade) wrote Re: Unit in error, yet juju resolved claims it's fixed | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
@ahasenack, juju expects that you'll use juju to manipulate the environment. Deliberately terminating an instance out-of-band is not supported behaviour at the moment; so I think the precise expression of the original bug is "invalid".
@davidpbritton, just to be clear (with no implication that it's not-a-bug): I think that that use case *will* recover; it will just take a while to do so. I absolutely agree that it could and should be done faster when the unit agent's not running. If that's not the case, please post a status demonstrating the stuckness of deploy/
Either way, I think this bug can be actionably characterized as "units of destroyed services are not destroyed if their agents are not running"; and fixing that will clearly improve the experience in both the described use cases. Sensible?