Comment 1 for bug 853920

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.

Excerpts from Roger Peppe's message of Mon Sep 19 14:44:11 UTC 2011:
> Public bug reported:
>
> When running juju debug-log, I would expect it to finish when the juju environment
> is destroyed. Instead, I see something like the following output, and then nothing more.
>
> 2011-09-19 15:36:50,907 ERROR SSH forwarding error: Connection to
> ec2-50-16-111-175.compute-1.amazonaws.com closed by remote host.
>
> Unhandled error in Deferred:
> Traceback (most recent call last):
> Failure: juju.errors.NoConnection: SSH forwarding error: Connection to ec2-50-16-111-175.compute-1.amazonaws.com closed by remote host.
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>