Comment 8 for bug 1219902
Revision history for this message
| Merlijn Sebrechts (merlijn-sebrechts) wrote | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
I'd like to point out that the `juju resolved` workaround is not ideal for us. We deploy services that manage other clouds. When installation fails and we issue `juju resolved`, the service will start to manage the cloud environment as if nothing went wrong. This will fail in very unpredictable and possibly destructive ways.
For the moment, the only thing we can do is `juju destroy-service` and `juju destroy-machine --force`. This works when the service is deployed inside a container, but we can't use this method when the service is on a physical machine, or we'd lose the physical machine...
Destroy-service waiting for the stop hook is a very good default. Having a way to tell Juju "skip the queue and remove this service NOW" would be really helpful for us...