destroy-environment hangs if it cannot connect to the API server

[John A Meinel]

I know we want to teardown gracefully when we can, but I just ran "juju destroy-environment -y local" and it stuck there for at least 5 minutes.
I ^C and ran it again with --debug and it is spinning on:
2014-04-18 09:42:11 INFO juju.state.api apiclient.go:198 dialing "wss://10.0.3.1:17070/"
2014-04-18 09:42:11 DEBUG juju.state.api apiclient.go:204 error dialing "wss://10.0.3.1:17070/", will retry: websocket.Dial wss://10.0.3.1:17070/: dial tcp 10.0.3.1:17070: connection refused

I don't mind if it retries for a bit, but even 5 minutes is a bit long, and I certainly would expect it to eventually give up and at least prompt that I might want to use "--force". (I don't mind terribly if it doesn't do it itself, since maybe you need to investigate why things aren't running like you thought they were.)

[John A Meinel (jameinel)]

I just ran into this again, and wanted to file it again. Good thing my browser history remembered it.
Really, the command just sits there blankly forever, which is bad UI.

[James Troup (elmo)]

This looks like a duplicate of LP #1413052

[Anastasia (anastasia-macmood)]

There have been a lot of changes in the area, especially for both -destroy-model and -controller equivalent. We believe this to be resolved.

If you are still seeing issues with Juju2, please file a bug on "juju" launchpad project with newer logs.