[
https://issues.apache.org/jira/browse/JCLOUDS-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14263538#comment-14263538
]
Aled Sage commented on JCLOUDS-207:
-----------------------------------
There seems to be eventual consistency within EC2 for detecting when the
security group is no longer in use. After terminating the VM, it can take
anywhere from immediate to several minutes before an attempted deletion of the
security group will succeed (it fails if it thinks there is still a VM using
the security group). jclouds does a retry 3 times to delete it, but it doesn't
wait for several minutes.
An alternative could be: on delete, query EC2 to find the VMs using the
security group, and then query those VMs' states to see if they are not
termianted (or short-cut that if we know we currently deleting the only VM in
that list) - we could then keep trying for 5 or 10 minutes. But that doesn't
sound ideal either.
> Key Pair and Security Groups created by jclouds are not removed when the node
> is destroyed (via Jclouds)
> --------------------------------------------------------------------------------------------------------
>
> Key: JCLOUDS-207
> URL: https://issues.apache.org/jira/browse/JCLOUDS-207
> Project: jclouds
> Issue Type: Bug
> Affects Versions: 1.6.0
> Reporter: Eugen Paraschiv
> Labels: ec2
>
> Simply stated, the problem is that the nodes that are created in EC2 via
> jclouds leave a key-pair and a security group each, after they're deleted
> (also via jclouds).
> This issue is described in much more detail here:
> http://www.cloudsoftcorp.com/blog/tidying-up-after-jclouds/
> Hopefully it's an easy fix and the operation of first creating and then
> destroying the node will leave no unnecessary artifacts on the EC2 account.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
