[
https://issues.apache.org/jira/browse/WHIRR-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13670760#comment-13670760
]
Andrew Bayer commented on WHIRR-725:
------------------------------------
Yeah, I was trying the password from startup on the console too. Ok, I guess I
need to figure out how to make jclouds play nicely with CloudStack named
keypairs then. =) And they need to fix whatever's going on there with
cloud-init and keys. I'll see if I can find some hack way to get Whirr+jclouds
to use named keypairs - jclouds is expecting to find the private key for the
named keypair somewhere in memory, but it's a rather old credential store that
isn't in use almost anywhere else. I'll see what I can figure out.
> Security Group rules don't get created on CloudStack 4.0.2 provider
> -------------------------------------------------------------------
>
> Key: WHIRR-725
> URL: https://issues.apache.org/jira/browse/WHIRR-725
> Project: Whirr
> Issue Type: Bug
> Components: new provider, service/hadoop
> Affects Versions: 0.8.2
> Environment: Running Whirr 0.8.2 on OSX 10.8.2, compiled from source.
> Using a cloudstack 4.0.2 cloud.
> Reporter: sebastien goasguen
> Attachments: console.jpg, whirr.properties
>
>
> Trying to deploy a cdh cluster, the instances start, nodes get configured.
> But the security groups rules don't get created/added to the SG. No errors in
> the whirr.log file.
> Adding the rules by hand, out of band from whirr fixes the issue. Instances
> get a working hadoop (at least hadoop fs -ls / works).
--
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
