[WHIRR-264] JClouds is unable to do SSH on automatically selected images

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Not A Problem
• Fix Version/s: 0.4.0
• Assignee: Adrian Cole (Inactive)
• Reporter: Andrei Savu
• Created: 16/Mar/11 16:55
• Updated: 17/Mar/11 17:04
• Resolved: 17/Mar/11 17:04

Description

I'm seeing the following exception when trying to start a cluster and when running integration tests without specifying an AMI and an instance type:

org.jclouds.ssh.SshException: ec2-user@184.72.64.23:22: Error connecting to session.
	at org.jclouds.ssh.jsch.JschSshClient.propagate(JschSshClient.java:252)
	at org.jclouds.ssh.jsch.JschSshClient.connect(JschSshClient.java:206)
	at org.jclouds.compute.callables.RunScriptOnNodeAsInitScriptUsingSsh.call(RunScriptOnNodeAsInitScriptUsingSsh.java:90)
	at org.jclouds.compute.strategy.RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:70)
	at org.jclouds.compute.strategy.RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:45)
	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:662)
Caused by: com.jcraft.jsch.JSchException: Auth fail
	at com.jcraft.jsch.Session.connect(Session.java:461)
	at com.jcraft.jsch.Session.connect(Session.java:154)
	at org.jclouds.ssh.jsch.JschSshClient.newSession(JschSshClient.java:247)
	at org.jclouds.ssh.jsch.JschSshClient.connect(JschSshClient.java:186)
	... 8 more

I have been able to run the entire test suite when I changed the properties files and specified an image and a instance type (ubuntu 10.4 on machine with 2GB or more).

You can reproduce the problem by trying to run the ZooKeeper recipe:
$ ./bin/whirr launch-cluster --config recipes/zookeeper-ec2.properties

I've experienced this problem with the following ami: us-east-1/ami-8e1fece7 running on a t1.micro instance type.