[
https://issues.apache.org/jira/browse/JCLOUDS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14260444#comment-14260444
]
Aled Sage commented on JCLOUDS-529:
-----------------------------------
See fix in https://github.com/jclouds/jclouds/pull/629 (against 1.8.x branch
currently).
Previously, the error code was always `InvalidGroup.InUse`. Now some people are
getting `DependencyVioloation`.
In
http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DeleteSecurityGroup.html
it says: "the operation fails with InvalidGroup.InUse in EC2-Classic or
DependencyViolation in EC2-VPC". I wonder if a default has been changed for new
accounts versus old accounts perhaps?
The fix is simple: to interpret the `DependencyVioloation` in the same was as
the `InUse`.
> Getting exception while destroying an aws instance using jclouds
> ----------------------------------------------------------------
>
> Key: JCLOUDS-529
> URL: https://issues.apache.org/jira/browse/JCLOUDS-529
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute, jclouds-core
> Reporter: supraja
>
> Getting the below Exception while trying to destroy an aws instance using
> destroyNode(id)
> org.jclouds.aws.AWSResponseException: request POST
> https://ec2.us-east-1.amazonaws.com/ HTTP/1.1 failed with code 400, error:
> AWSError{requestId='2de
> fa53c-fd1f-4cad-b547-4ffd2158e020', requestToken='null',
> code='DependencyViolation', message='resource sg-ba812bdf has a dependent
> object', context='{Response=,
> Errors=}'}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
