Uploaded image for project: 'jclouds'
  1. jclouds
  2. JCLOUDS-1331

Azure ARM orphaned resource groups are not cleaned up due to api caching/timing issue

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • 2.0.2
    • None
    • jclouds-compute

    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.

      Attachments

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            duncanjg Duncan Grant
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:

              Slack

                Issue deployment