> + assertPosted(DEFAULT_REGION,
> "Action=DescribePlacementGroups&GroupName.1=jclouds%23sg-3c6ef654%23us-east-1");
> + assertPosted(DEFAULT_REGION,
> "Action=DeletePlacementGroup&GroupName=jclouds%23sg-3c6ef654%23us-east-1");
> + assertPosted(DEFAULT_REGION,
> "Action=DescribePlacementGroups&GroupName.1=jclouds%23sg-3c6ef654%23us-east-1");
> + }
> +
> + public void
> deleteIncidentalResourcesGivingDependencyViolationForSecurityGroup() throws
> Exception {
> +
> runDeleteIncidentalResourcesGivingErrForSecurityGroup("DependencyViolation");
> + }
> +
> + public void deleteIncidentalResourcesGivingInUseForSecurityGroup() throws
> Exception {
> +
> runDeleteIncidentalResourcesGivingErrForSecurityGroup("InvalidGroup.InUse");
> + }
> +
> + protected void
> runDeleteIncidentalResourcesGivingErrForSecurityGroup(String errCode) throws
> Exception {
> + // Complicated dispatcher is needed because cleanUpIncidentalResources
> will retry an unpredictable
> + // number of times (because it is time-based, for 3 seconds - not
> configurable).
@nacx agreed that making this configurable is sensible. I'd prefer that work to
be done in multiple stages if possible - with this PR being merged first, as it
fixes the issue of delete-VM always failing for a sub-set of AWS account
holders.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/629/files#r22782327
