Graeme Miller created BROOKLYN-529:
--------------------------------------
Summary: Windows location keyPair issue
Key: BROOKLYN-529
URL: https://issues.apache.org/jira/browse/BROOKLYN-529
Project: Brooklyn
Issue Type: Bug
Reporter: Graeme Miller
I can't deploy the following blueprint
{{name: bad
location:
'jclouds:aws-ec2':
region: eu-west-1
identity: xxx
credential: xxx
imageOwner: 801119661308
imageNameRegex: Windows_Server-2012-R2_RTM-English-64Bit-Base-.*
useJcloudsSshInit: false
keyPair: myKeypair
services:
- type: org.apache.brooklyn.entity.software.base.VanillaWindowsProcess
brooklyn.config:
install.command: echo installing
checkRunning.command: echo running}}
while the slightly modified version
{{name: bad
location:
'jclouds:aws-ec2':
region: eu-west-1
identity: xxx
credential: xxx
imageOwner: 801119661308
imageNameRegex: Windows_Server-2012-R2_RTM-English-64Bit-Base-.*
useJcloudsSshInit: false
services:
- type: org.apache.brooklyn.entity.software.base.VanillaWindowsProcess
brooklyn.config:
install.command: echo installing
checkRunning.command: echo running}}
works fine.
if you specify a keyPair, jclouds won’t wait for the admin password to be ready
and will return the node without password; while if the blueprint doesn’t
specify a keyPair name, jclouds will generate one and will use the private key
to decrypt the admin password and pass back to brooklyn a node with a valid
`LoginCredentials.password`
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)