jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-105) CloudStack instance provisioning uses password if passwordEnabled, even if a keypair is given
Date Fri, 31 May 2013 20:43:20 GMT

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

ASF subversion and git services commented on JCLOUDS-105:
---------------------------------------------------------

Commit f615eb11a378fcce9c5e9dde839dd87de311e59c in branch refs/heads/1.6.x from [~abayer]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;h=f615eb1 ]

JCLOUDS-105. Short-term fix for keypairs being ignored if VM says it's password-enabled.

                
> CloudStack instance provisioning uses password if passwordEnabled, even if a keypair
is given
> ---------------------------------------------------------------------------------------------
>
>                 Key: JCLOUDS-105
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-105
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-compute
>    Affects Versions: 1.5.10, 1.6.0
>            Reporter: Andrew Bayer
>            Assignee: Andrew Bayer
>             Fix For: 1.7.0, 1.6.1
>
>
> In the process of trying to figure out WHIRR-725, I eventually discovered that CloudStackComputeServiceAdapter.createNodeWithGroupEncodedIntoName
will set the initial credentials for the VM to be the autogenerated password no matter what,
if passwordEnabled=true on the VM, even if you've explicitly specified an SSH keypair. This
caused problems with init scripts (i.e., they couldn't run since it couldn't authenticate)
with exoscale, who have passwordEnabled=true on their images, but block password authentication
over SSH. 
> There's a pretty easy fix for this - in the method in question, just flip it so that
the password option is only used if passwordEnabled is true *and* there is no keypair specified
in the template options. Patch incoming.

--
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

Mime
View raw message