[JCLOUDS-1332] BaseComputeService.destroyNodesMatching and BaseComputeService.destroyNode different behavior

• Type: Bug
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: 2.0.1, 2.0.2
• Component/s: jclouds-compute
• Assignee: Andrea Turli
• Reporter: Andrea Turli
• Created: 25/Aug/17 15:53
• Updated: 30/Nov/17 07:42

Description

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

Issue Links

• links to: GitHub Pull Request #805