jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrea Turli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-1329) Azure ARM extraneous resources are not cleaned up on node deletion
Date Thu, 24 Aug 2017 14:43:00 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140106#comment-16140106

Andrea Turli commented on JCLOUDS-1329:

Thanks [~duncangrant]

Reading https://github.com/jclouds/jclouds-labs/blob/master/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/compute/AzureComputeServiceAdapter.java#L330
I'd have expected `cleanupResources.cleanupNode(id)` was able to delete the vm and most of
the resources associated.
Then the `AdaptingComputeServiceStrategies.destroyNode` to collect the NodeMetadata before
the deletion and to return it to be used in cleanUpIncidentalResourcesOfDeadNodes.

When are you seeing this problem, during normal flow or in exceptional situations?

> 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
> 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

View raw message