nakomis commented on this pull request.
> @@ -171,9 +216,12 @@ public boolean cleanupSecurityGroupIfOrphaned(String
> resourceGroup, String group
logger.debug(">> deleting orphaned security group %s from
%s...", name, resourceGroup);
try {
deleted = resourceDeleted.apply(sgapi.delete(name));
+
resourceRemoved.apply(IdReference.create(securityGroup.id()));
Unfortunately, yes, we do need to wait. The issue that this PR is addressing is
that even through a resource is deleted and (in this case) the
NetworkSecuityGroup API is showing that group has been deleted, it is still
showing up in the ResourceGroup. This appears to be an "eventual consistency"
issue, so we need to wait until the resource no longer shows as a member of the
resource group
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1240#discussion_r235384528
