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

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 2.0.2
• Component/s: jclouds-compute
• Labels: azurecompute-arm
• Assignee: Unassigned
• Reporter: Duncan Grant
• Created: 25/Aug/17 10:30
• Updated: 06/Feb/19 20:24

Description

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.