[WHIRR-637] Cannot Launch Cluster Using Whirr 0.7.1

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.7.1
• Component/s: service/cdh

Environment

osx

• Assignee: Unassigned
• Reporter: Joseph Misiti
• Created: 20/Aug/12 18:10
• Updated: 20/Aug/12 18:19

Description

Using the following hadoop.properties file:

whirr.cluster-name=myclsuter
whirr.instance-templates=1 hadoop-jobtracker+hadoop-namenode,1 hadoop-datanode+hadoop-tasktracker
whirr.provider=aws-ec2
whirr.identity=XXXXXX
whirr.credential=XXXXX
whirr.private-key-file=/home/ubuntu/.ssh/id_rsa
whirr.public-key-file=/home/ubuntu/.ssh/id_rsa.pub
whirr.hadoop-install-function=install_cdh_hadoop
whirr.hadoop-configure-function=configure_cdh_hadoop
whirr.hardware-id=m1.small
whirr.location-id=us-east-1

I cannot successfully launch a cluster on EC2 due to the following exceptions:

Caused by: org.jclouds.rest.AuthorizationException: (ubuntu:rsa[fingerprint(40:3c:de:7a:70:5f:7f:36:68:d5:ff:f2:62:97:18:21),sha1(89:08:b8:c8:65:0f:22:11:60:09:7e:94:fd:5f:10:be:4d:9f:f6:42)]@50.16.172.67:22) (ubuntu:rsa[fingerprint(40:3c:de:7a:70:5f:7f:36:68:d5:ff:f2:62:97:18:21),sha1(89:08:b8:c8:65:0f:22:11:60:09:7e:94:fd:5f:10:be:4d:9f:f6:42)]@50.16.172.67:22) error acquiring SSHClient(timeout=60000): Exhausted available authentication methods
at org.jclouds.sshj.SshjSshClient.propagate(SshjSshClient.java:413)
at org.jclouds.sshj.SshjSshClient.acquire(SshjSshClient.java:244)
at org.jclouds.sshj.SshjSshClient.connect(SshjSshClient.java:255)
at org.jclouds.compute.callables.RunScriptOnNodeAsInitScriptUsingSsh.call(RunScriptOnNodeAsInitScriptUsingSsh.java:89)
at org.jclouds.compute.internal.BaseComputeService.runScriptOnNode(BaseComputeService.java:612)
at org.apache.whirr.actions.ScriptBasedClusterAction$2.call(ScriptBasedClusterAction.java:190)
at org.apache.whirr.actions.ScriptBasedClusterAction$2.call(ScriptBasedClusterAction.java:178)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

If I change the config by specifying a particular AMI (found in Cloudera docs)

https://ccp.cloudera.com/display/CDHDOC/Whirr+Installation#WhirrInstallation-UpgradingWhirrtotheLatestCDH3Release

it works fine