[
https://issues.apache.org/jira/browse/JCLOUDS-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14532349#comment-14532349
]
ASF subversion and git services commented on JCLOUDS-207:
---------------------------------------------------------
Commit 31749cba5deb387064a60343604c4c3628b4d600 in jclouds's branch
refs/heads/master from [~hendrens]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=31749cb ]
JCLOUDS-207: Key Pair and Security Groups created by jclouds are not removed
when the node is destroyed
The names created do not match those searched for.
They are created in
FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat.java
and have are of this form jclouds#I-0#e96.
But for example jclouds#I-0#us-east-1#* is used as the search term.
> 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
> Components: jclouds-compute
> 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)
