You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Duncan Grant (JIRA)" <ji...@apache.org> on 2017/08/25 10:12:02 UTC
[jira] [Closed] (JCLOUDS-1329) Azure ARM extraneous resources are
not cleaned up on node deletion
[ https://issues.apache.org/jira/browse/JCLOUDS-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Duncan Grant closed JCLOUDS-1329.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.0.3
2.1.0
Fixed by https://github.com/jclouds/jclouds-labs/pull/409
> 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
> Fix For: 2.1.0, 2.0.3
>
>
> 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)