juju just hangs if Joyent gets stuck

[Aaron Bentley]

For example, juju destroy-environment --force just sits there. No errors, no "retrying" messages.
The user needs some kind of feedback.

$ juju --show-log destroy-environment --force test-final-relee-joyent
2014-09-04 19:19:36 INFO juju.cmd supercommand.go:37 running juju [1.20.7-trusty-amd64 gc]
WARNING! this command will destroy the "test-final-release-joyent" environment (type: joyent)
This includes all machines, services, data and other resources.

Continue [y/N]? y
2014-09-04 19:19:38 INFO juju.provider.common destroy.go:15 destroying environment "test-final-release-joyent"
^C
$ date --utc
Thu Sep 4 19:25:37 UTC 2014

[Curtis Hovey (sinzui)]

We can see that instances in joyent get stuck in provisioning. When this happens, we need to open a support request to delete the machine. We also believe that once a machine is stuck in provisioning, when we try to create a new env, we are handed the broken machine by joyent.

[Aaron Bentley (abentley)]

As seen in bug #1400375 it can hang more than 2 days.

[Anastasia (anastasia-macmood)]

Looking at the latest CI runs against master (Juju 2), all joyent jobs have run successfully and happily.

This issue looks to be resolved by other improvements in joyent provider since this bug was filed.