[
https://issues.apache.org/jira/browse/WHIRR-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13670739#comment-13670739
]
Andrew Bayer commented on WHIRR-725:
------------------------------------
Ah, yeah, whirr.client-cidrs=0.0.0.0/0 (or whatever value you want there).
And any instance I create, either through Whirr or through the exoscale UI,
isn't setting the password for ubuntu (or root) that it claims to have used,
and in fact, when I set one instance up with a keypair and SSH'd in, I could
see that the password hadn't been updated at all. So something's definitely
awry there - and I have yet to figure out a way to use named keypairs for
CloudStack with whirr, so, hey, fun. =)
> 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: 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
