[
https://issues.apache.org/jira/browse/JCLOUDS-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140142#comment-16140142
]
Duncan Grant commented on JCLOUDS-1329:
---------------------------------------
[~andreaturli] I see this during normal flow.
I think that you are correct that
`AdaptingComputeServiceStrategies.destroyNode` will return the node metadata
but during the retry step in 'BaseComputeService.doDestroyNode' the metadata
gets lost. This happens during the nodeTerminated.apply(node) call which sets
the metadata in the "node" AtomicReference to the metadata returned from the
api which happens to be null. I really struggle with the guice injection stuff
so I can't seem to find the exact bit of code where this happens. Let me know
if you want to screen share and we could step through with a debugger.
thanks
> Azure ARM extraneous resources are not cleaned up on node deletion
> ------------------------------------------------------------------
>
> Key: JCLOUDS-1329
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1329
> Project: jclouds
> Issue Type: Bug
> Affects Versions: 2.0.2
> Reporter: Duncan Grant
>
> This is because doDestroyNode returns null once a node has been deleted so
> there is no node metadata to use to cleanup the extraneous resources.
> This is particularly problematic on Azure ARM as the resource limits are
> quite low be default for some of these resources so you can quickly get into
> a state where you can't deploy nodes.
> I've created a PR based on equivalent GCE compute code to fix this.
> https://github.com/jclouds/jclouds-labs/pull/409
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
