Comment 2 for bug 853920
Revision history for this message
| Clint Byrum (clint-fewbar) wrote Re: [Bug 853920] [NEW] debug-log does not terminate when the environment is destroyed | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Excerpts from Kapil Thangavelu's message of Mon Sep 19 16:00:23 UTC 2011:
> I just wanted to explain why this behavior exists.
>
> Right now destroy-environment is entirely client-side to ensure that its robust,
> regardless of the state of the environment. Ie. any number of critical
> infrastructure pieces could be dead, and destroy-environment will still work.
>
> This of course makes coordination around environment destruction
> difficult.
That makes perfect sense.
We could have a best-effort try to set something in zookeeper that says
basically "environment is doomed" so they can gracefully give up if they
happen to get that message, right?
I've experienced this before, so setting status to Confirmed.
This being an annoyance and not really breaking any functionality,
setting importance to Low,