[
https://issues.apache.org/jira/browse/JCLOUDS-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignasi Barrera updated JCLOUDS-1332:
------------------------------------
Fix Version/s: (was: 2.0.4)
(was: 2.1.0)
> BaseComputeService.destroyNodesMatching and BaseComputeService.destroyNode
> different behavior
> ---------------------------------------------------------------------------------------------
>
> Key: JCLOUDS-1332
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1332
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute
> Affects Versions: 2.0.1, 2.0.2
> Reporter: Andrea Turli
> Assignee: Andrea Turli
> Priority: Critical
>
> DestroyNode doesn't clean up incidental resources as the destroyNodesMatching
> does.
> In fact, nodeTerminate.apply(node) has a side-effect and set node=null
> Potential fixes:
> - return `md` instead of node.get
> or
> - TrueIfNullOrDeletedRefreshAndDoubleCheckOnFalse predicate to return true
> when `refreshOrNull` return null
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
