You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "Alasdair Hodge (JIRA)" <ji...@apache.org> on 2017/02/02 09:56:51 UTC

[jira] [Created] (BROOKLYN-432) "Unmanage" operation leads to dangling references (rebind errors)

Alasdair Hodge created BROOKLYN-432:
---------------------------------------

             Summary: "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


"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)