[
https://issues.apache.org/jira/browse/JCLOUDS-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140198#comment-16140198
]
Andrea Turli commented on JCLOUDS-1329:
---------------------------------------
Interesting point about the retry step in `BaseComputeService.doDestroyNode`, I
think this is a smell of a problem with the core if ARM and GCE needed to "fix"
the default behavior, but something for another issue, cc [~nacx]
> 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)
