Uploaded image for project: 'jclouds'
  1. jclouds
  2. JCLOUDS-1332

BaseComputeService.destroyNodesMatching and BaseComputeService.destroyNode different behavior

    Details

    • Type: Bug
    • Status: Open
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: 2.0.1, 2.0.2
    • Fix Version/s: None
    • Component/s: jclouds-compute
    • Labels:
      None

      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

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                andreaturli Andrea Turli
                Reporter:
                andreaturli Andrea Turli
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: