You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@jclouds.apache.org by "Andrea Turli (JIRA)" <ji...@apache.org> on 2017/08/25 15:54:00 UTC

[jira] [Created] (JCLOUDS-1332) BaseComputeService.destroyNodesMatching and BaseComputeService.destroyNode different behavior

Andrea Turli created JCLOUDS-1332:
-------------------------------------

             Summary: 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.2, 2.0.1
            Reporter: Andrea Turli
            Assignee: Andrea Turli
            Priority: Critical
             Fix For: 2.1.0, 2.0.3


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)