[
https://issues.apache.org/jira/browse/BROOKLYN-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15853725#comment-15853725
]
Alasdair Hodge commented on BROOKLYN-432:
-----------------------------------------
NOTE: it seems that "unmanaging" a jclouds machine location also releases the
underlying VM. I can see no method to simply remove the location from the
management context.
> "Unmanage" operation leads to dangling references (rebind errors)
> -----------------------------------------------------------------
>
> Key: BROOKLYN-432
> URL: https://issues.apache.org/jira/browse/BROOKLYN-432
> Project: Brooklyn
> Issue Type: Bug
> Affects Versions: 0.9.0, 0.10.0, 0.11.0
> Reporter: Alasdair Hodge
> Assignee: Alasdair Hodge
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> "Unmanaging" an entity via the web UI does not clean up its locations,
> leading to orphans in the management context and persisted state. In itself,
> this is a (minor) bug, but more seriously: orphaned
> {{JcloudsSshMachineLocation}} instances contain references to the unmanaged
> entity, which subsequently causes dangling-reference errors on rebind.
> Suggest always pruning orphans from the management context whenever an entity
> is unmanaged. Can't think of a valid use-case where this isn't the desired
> behaviour.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
