[jira] [Updated] (JCLOUDS-1331) Azure ARM orphaned resource groups are not cleaned up due to api caching/timing issue

2019-02-06 Thread Andrew Gaul (JIRA)


 [ 
https://issues.apache.org/jira/browse/JCLOUDS-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Gaul updated JCLOUDS-1331:
-
Fix Version/s: (was: 2.1.2)

> Azure ARM orphaned resource groups are not cleaned up due to api 
> caching/timing issue
> -
>
> Key: JCLOUDS-1331
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1331
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute
>Affects Versions: 2.0.2
>Reporter: Duncan Grant
>Priority: Minor
>  Labels: azurecompute-arm
>
> When an azure arm node, and all of its resources, are deleted the resource 
> group is not deleted.  This is because there is a short period of time when 
> the ARM api call here: 
> https://github.com/duncangrant/jclouds-labs/blob/dbadb279f14848f21879f7eb6c7136e1a5f11192/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/compute/strategy/CleanupResources.java#L207
> will respond with a list of resources even though they have been deleted.
> Presumably this could be fixed with a) a retry step or b) by deleting the 
> resource group anyway if we know that we have already deleted all the 
> resources in it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (JCLOUDS-1331) Azure ARM orphaned resource groups are not cleaned up due to api caching/timing issue

2018-08-16 Thread Ignasi Barrera (JIRA)


 [ 
https://issues.apache.org/jira/browse/JCLOUDS-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ignasi Barrera updated JCLOUDS-1331:

Fix Version/s: (was: 2.1.1)
   2.1.2

> Azure ARM orphaned resource groups are not cleaned up due to api 
> caching/timing issue
> -
>
> Key: JCLOUDS-1331
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1331
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute
>Affects Versions: 2.0.2
>Reporter: Duncan Grant
>Priority: Minor
>  Labels: azurecompute-arm
> Fix For: 2.1.2
>
>
> When an azure arm node, and all of its resources, are deleted the resource 
> group is not deleted.  This is because there is a short period of time when 
> the ARM api call here: 
> https://github.com/duncangrant/jclouds-labs/blob/dbadb279f14848f21879f7eb6c7136e1a5f11192/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/compute/strategy/CleanupResources.java#L207
> will respond with a list of resources even though they have been deleted.
> Presumably this could be fixed with a) a retry step or b) by deleting the 
> resource group anyway if we know that we have already deleted all the 
> resources in it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (JCLOUDS-1331) Azure ARM orphaned resource groups are not cleaned up due to api caching/timing issue

2018-02-20 Thread Andrea Turli (JIRA)

 [ 
https://issues.apache.org/jira/browse/JCLOUDS-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Turli updated JCLOUDS-1331:
--
Fix Version/s: 2.0.4

> Azure ARM orphaned resource groups are not cleaned up due to api 
> caching/timing issue
> -
>
> Key: JCLOUDS-1331
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1331
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute
>Affects Versions: 2.0.2
>Reporter: Duncan Grant
>Priority: Minor
>  Labels: azurecompute-arm
> Fix For: 2.0.4
>
>
> When an azure arm node, and all of its resources, are deleted the resource 
> group is not deleted.  This is because there is a short period of time when 
> the ARM api call here: 
> https://github.com/duncangrant/jclouds-labs/blob/dbadb279f14848f21879f7eb6c7136e1a5f11192/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/compute/strategy/CleanupResources.java#L207
> will respond with a list of resources even though they have been deleted.
> Presumably this could be fixed with a) a retry step or b) by deleting the 
> resource group anyway if we know that we have already deleted all the 
> resources in it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (JCLOUDS-1331) Azure ARM orphaned resource groups are not cleaned up due to api caching/timing issue

2017-09-05 Thread Andrew Gaul (JIRA)

 [ 
https://issues.apache.org/jira/browse/JCLOUDS-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Gaul updated JCLOUDS-1331:
-
Labels: azurecompute-arm  (was: )

> Azure ARM orphaned resource groups are not cleaned up due to api 
> caching/timing issue
> -
>
> Key: JCLOUDS-1331
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1331
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute
>Affects Versions: 2.0.2
>Reporter: Duncan Grant
>Priority: Minor
>  Labels: azurecompute-arm
>
> When an azure arm node, and all of its resources, are deleted the resource 
> group is not deleted.  This is because there is a short period of time when 
> the ARM api call here: 
> https://github.com/duncangrant/jclouds-labs/blob/dbadb279f14848f21879f7eb6c7136e1a5f11192/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/compute/strategy/CleanupResources.java#L207
> will respond with a list of resources even though they have been deleted.
> Presumably this could be fixed with a) a retry step or b) by deleting the 
> resource group anyway if we know that we have already deleted all the 
> resources in it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (JCLOUDS-1331) Azure ARM orphaned resource groups are not cleaned up due to api caching/timing issue

2017-09-05 Thread Andrew Gaul (JIRA)

 [ 
https://issues.apache.org/jira/browse/JCLOUDS-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Gaul updated JCLOUDS-1331:
-
Component/s: jclouds-compute

> Azure ARM orphaned resource groups are not cleaned up due to api 
> caching/timing issue
> -
>
> Key: JCLOUDS-1331
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1331
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute
>Affects Versions: 2.0.2
>Reporter: Duncan Grant
>Priority: Minor
>  Labels: azurecompute-arm
>
> When an azure arm node, and all of its resources, are deleted the resource 
> group is not deleted.  This is because there is a short period of time when 
> the ARM api call here: 
> https://github.com/duncangrant/jclouds-labs/blob/dbadb279f14848f21879f7eb6c7136e1a5f11192/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/compute/strategy/CleanupResources.java#L207
> will respond with a list of resources even though they have been deleted.
> Presumably this could be fixed with a) a retry step or b) by deleting the 
> resource group anyway if we know that we have already deleted all the 
> resources in it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)