[
https://issues.apache.org/jira/browse/WHIRR-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13221125#comment-13221125
]
Joris Poort edited comment on WHIRR-378 at 3/2/12 6:15 PM:
-----------------------------------------------------------
Seems like it might have been defining "whirr.bootstrap-user" instead of
"whirr.login-user" caused the issue. Seems odd, but right now I've tracked it
down to the following: custom AMI (standard OS, private or public) in
combination with definition of either ("bootstrap-user" or no "login-user" -
not sure which one) specified causes the issue.
was (Author: gpoort):
Seems like it might have been defining "whirr.bootstrap-user" instead of
whirr.login-user caused the issue. Seems odd, but right now I've tracked it
down to the following: custom AMI (standard OS, private or public) in
combination with definition of either ("bootstrap-user" or no "login-user" -
not sure which one) specified causes the issue.
> Auth fail when creating a cluster from an EC2 instance
> ------------------------------------------------------
>
> Key: WHIRR-378
> URL: https://issues.apache.org/jira/browse/WHIRR-378
> Project: Whirr
> Issue Type: Bug
> Components: service/hadoop
> Affects Versions: 0.6.0
> Reporter: Marc de Palol
> Assignee: Adrian Cole
> Priority: Critical
> Fix For: 0.8.0
>
> Attachments: run-test.sh, setup-whirr.sh
>
>
> There is a ssh auth problem when creating a hadoop cluster from an EC2 ubuntu
> instance.
> I've been using the same configuration file from an EC2 computer an a
> physical one, everything works fine in the physical one, but I keep getting
> this error in EC2:
> Running configuration script on nodes: [us-east-1/i-c7fde5a6,
> us-east-1/i-c9fde5a8, us-east-1/i-cbfde5aa]
> <<authenticated>> woke to: net.schmizz.sshj.userauth.UserAuthException:
> publickey auth failed
> <<authenticated>> woke to: net.schmizz.sshj.userauth.UserAuthException:
> publickey auth failed
> The user in the virtual machine is new and with valid .ssh keys.
> The hadoop config file is (omitting commented lines):
> whirr.cluster-name=hadoop
> whirr.instance-templates=1 hadoop-namenode+hadoop-jobtracker,3
> hadoop-datanode+hadoop-tasktracker
> whirr.provider=aws-ec2
> whirr.identity=****
> whirr.credential=****
> whirr.hardware-id=c1.xlarge
> whirr.image-id=us-east-1/ami-da0cf8b3
> whirr.location-id=us-east-1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira