Github user aledsage commented on the issue:
https://github.com/apache/brooklyn-server/pull/487
@neykov @drigodwin for VMs being "orphaned", not managed by Brooklyn, I
think it's good enough for now. The only times I know of it happening are:
1. When Brooklyn was terminated during provisioning (before it got the VM
id back from jclouds) - i.e. https://issues.apache.org/jira/browse/BROOKLYN-264
2. When the cloud gives us an error, when we try to delete the VM (e.g.
https://issues.apache.org/jira/browse/BROOKLYN-411)
For (2), there's not much we can do - but we could improve things a bit:
1. Try to handle such cases in jclouds (but for BROOKLYN-411 we already
retried 6 times!)
2. Raise an event that the VM is "orphaned" (requires a better place to
push such events, rather than just the info log; that's a separate topic!)
Of course if someone also sets `destroyOnFailure: false` then we'll leave
behind an orphaned VM!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
