Andrew Bayer created JCLOUDS-105:
------------------------------------
Summary: 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.6.0, 1.5.10
Reporter: Andrew Bayer
Assignee: Andrew Bayer
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
