[
https://issues.apache.org/jira/browse/JCLOUDS-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140177#comment-16140177
]
Duncan Grant commented on JCLOUDS-1329:
---------------------------------------
I've debugged through and it happens here:
https://github.com/duncangrant/jclouds/blob/9cdd53b0b7a87fa26a77b9ce370882f2a9cc7d71/compute/src/main/java/org/jclouds/compute/predicates/internal/TrueIfNullOrDeletedRefreshAndDoubleCheckOnFalse.java#L47
> 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)
