[
https://issues.apache.org/jira/browse/JCLOUDS-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370300#comment-16370300
]
Jim Spring commented on JCLOUDS-1330:
-------------------------------------
I think a specific deletion of a resource group should delete all resources in
it regardless of who created the resources.
In this case, if the resources were created with jclouds, we should delete them
like the network and the RG if empty. If non-jclouds resources were added to
the RG, then they shouldn’t be deleted (unless the user specifies a specific RG
delete).
One option would be to use tags to specify jclouds created resources.
Sent from my iThingy
> Azure ARM orphaned networks not cleaned up when node deleted
> ------------------------------------------------------------
>
> Key: JCLOUDS-1330
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1330
> 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
>
>
> Azure ARM orphaned networks not cleaned up when node deleted which also
> prevents the resource group from being removed.
> Not sure this is actually a bug.
> According to
> https://github.com/duncangrant/jclouds-labs/blob/dbadb279f14848f21879f7eb6c7136e1a5f11192/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/compute/strategy/CleanupResources.java#L94-L95
> the network should be cleaned up when the resource group is deleted.
> However this is not the case. As can be seen here:
> https://github.com/duncangrant/jclouds-labs/blob/dbadb279f14848f21879f7eb6c7136e1a5f11192/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/compute/strategy/CleanupResources.java#L207
> As the resource group contains the network this will prevent the resource
> group from being deleted leaving both the network and the resource group.
> I think that, assuming the network was created by jclouds at the same time as
> the resource group, it is reasonable to delete both here.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
