[JCLOUDS-105] CloudStack instance provisioning uses password if passwordEnabled, even if a keypair is given

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.10, 1.6.0
• Fix Version/s: 1.6.1, 1.7.0
• Component/s: jclouds-compute
• Assignee: Andrew Bayer
• Reporter: Andrew Bayer
• Created: 30/May/13 23:00
• Updated: 17/Jul/14 12:20
• Resolved: 31/May/13 20:43

Description

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.

Issue Links

• relates to: JCLOUDS-106 Modernize CloudStack instance credentials and security group code