libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomaz Muraus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LIBCLOUD-475) Different name for key_pair in node in Ec2 and Openstack driver
Date Fri, 27 Dec 2013 14:51:51 GMT

    [ https://issues.apache.org/jira/browse/LIBCLOUD-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13857512#comment-13857512
] 

Tomaz Muraus commented on LIBCLOUD-475:
---------------------------------------

Can you please also sync your branch with latest trunk and re-generate the patch?

I have troubles applying it cleanly:

{code}
Applying: LIBCLOUD-475 fix key_name in ec2 and cloudstack
error: patch failed: libcloud/compute/drivers/cloudstack.py:1497
error: libcloud/compute/drivers/cloudstack.py: patch does not apply
error: patch failed: libcloud/test/compute/test_cloudstack.py:248
error: libcloud/test/compute/test_cloudstack.py: patch does not apply
Patch failed at 0001 LIBCLOUD-475 fix key_name in ec2 and cloudstack
The copy of the patch that failed is found in:
{code}

> Different name for key_pair in node in Ec2 and Openstack driver
> ---------------------------------------------------------------
>
>                 Key: LIBCLOUD-475
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-475
>             Project: Libcloud
>          Issue Type: Bug
>            Reporter: Oleg Suharev
>            Priority: Minor
>         Attachments: LIBCLOUD-475.patch
>
>
> I detect in source code different name for keypair name in extra parameters for node.
In Amazon and Cloudstack it called 'keyname' but in Openstack driver it - 'key_name'.
> I can rename it on Openstack or Ec2/Cloudstack if You say what variant I must use.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message