[
https://issues.apache.org/jira/browse/JCLOUDS-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162125#comment-16162125
]
Jim Spring commented on JCLOUDS-1330:
-------------------------------------
I'll look at the diff, but is the proposal to delete the network when the node
associated with it is deleted? What if another resource is using that network?
If the resource group is deleted, then for sure the network should be as well
-- this is what happenes through the Azure portal, CLI, etc when you delete the
resource group.
Deleting a node, however, that is behavior different from using Azure directly.
What do other JClouds providers do in this case?
> 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
>
> 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
(v6.4.14#64029)
