[
https://issues.apache.org/jira/browse/DTACLOUD-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562628#comment-13562628
]
Marios Andreou commented on DTACLOUD-438:
-----------------------------------------
our ec2 driver is calling the CreateKeyPair method rather than the
ImportKeyPair... from the AWS API:
http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-CreateKeyPair.html
vs
http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-ImportKeyPair.html
from a quick look at the aws rubygem (currently 2.6.0) - import isn't yet
implemented. So we'll have to first open a pull request against that, before
adding the logic to the ec2 driver create_key method (see openstack driver for
example, which handles the import case).
working on it.
> Import SSH key into Amazon EC2 not working as expected
> ------------------------------------------------------
>
> Key: DTACLOUD-438
> URL: https://issues.apache.org/jira/browse/DTACLOUD-438
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Reporter: Enrique Fernandez Casado
> Assignee: Marios Andreou
>
> curl -X POST --user "user:pass" -F "name=mynewkey" -F "public_key=`cat
> /location/of/public/key/id_rsa.pub`"
> http://localhost:3001/api/keys?format=xml
> seems to be creating a new SSH key (using the provided key name) rather than
> importing the provided one
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
