[
https://issues.apache.org/jira/browse/JCLOUDS-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089559#comment-16089559
]
ASF subversion and git services commented on JCLOUDS-1318:
----------------------------------------------------------
Commit aa11765bee8e5e7f2d062ba8123c0dced822f071 in jclouds's branch
refs/heads/master from [~andreaturli]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=aa11765 ]
[JCLOUDS-1318] fix based on nodeTerminatePredicate
- wait for serer deletion, before deleting the security group
- rename cleanupServer to cleanupResources
- remove keyPairCache
- better usage of tags to remove securityGroups created by jclouds
- remove keyPair after the creation of a group
- remove test for create unique keypair
- openstack nova re-adding support for existing keypair
- fix securityGroupApi check
- fix other unit tests
- remove ServerPredicates as it is now duplicated
- remove TemplateOptions.securityGroupNames as deprecated
- address commits for
ApplyNovaTemplateOptionsCreatesNodesWithGroupEncodedIntoNameAndAddToSet
- fix testCreateNodeWhileUserSpecifiesKeyPairAndUserSpecifiedGroups
> Security group created for the server is not deleted
> ----------------------------------------------------
>
> Key: JCLOUDS-1318
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1318
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute
> Affects Versions: 2.0.1
> Reporter: Andrea Turli
> Assignee: Andrea Turli
> Fix For: 2.1.0, 2.0.3
>
>
> In some Openstack provider, during destroyNode the server gets deleted while
> the securityGroup created for it can't be deleted because of
> {{org.jclouds.http.HttpResponseException: command: DELETE
> https://compute.gra1.cloud.ovh.net/v2/68d8aaf362544fa78b040d7783fdad63/os-security-groups/f6957437-3035-463a-833f-253d21bc6c43
> HTTP/1.1 failed with response: HTTP/1.1 400 Bad Request; content:
> [{"badRequest": {"message": "Security Group
> f6957437-3035-463a-833f-253d21bc6c43 in use.", "code": 400}}]}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)