[
https://issues.apache.org/jira/browse/WHIRR-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135323#comment-13135323
]
Andrei Savu commented on WHIRR-410:
-----------------------------------
I'm running checks using the ZooKeeper integration tests.
With the os64Bit(true) call in place I get two machines t1.micro running AMI:
ebs/ubuntu-images/ubuntu-lucid-10.04-amd64-server-20110930 (ami-ad36fbc4) ant
the integration test works as expected.
Without the os64Bit(true) call I get two machines t1.micro running AMI:
ebs/ubuntu-images/ubuntu-lucid-10.04-i386-server-20110930 (ami-ab36fbc2) in
us-east-1c and ssh connectivity issues:
{noformat}
2011-10-25 21:34:54,166 WARN [jclouds.ssh] (user thread 1) <<
(ubuntu:rsa[fingerprint(75:ae:b7:5a:27:be:a2:4e:3f:a8:65:f0:08:51:2c:7e),sha1(09:45:59:83:4f:02:72:10:e6:6c:10:05:2f:21:51:1c:4d:95:21:5e)]@50.16.38.124:22)
error acquiring Session(): Timeout expired
net.schmizz.sshj.connection.ConnectionException: Timeout expired
at
net.schmizz.sshj.connection.ConnectionException$1.chain(ConnectionException.java:32)
at
net.schmizz.sshj.connection.ConnectionException$1.chain(ConnectionException.java:26)
at net.schmizz.concurrent.Promise.retrieve(Promise.java:139)
at net.schmizz.concurrent.Event.await(Event.java:103)
at
net.schmizz.sshj.connection.channel.direct.AbstractDirectChannel.open(AbstractDirectChannel.java:68)
at net.schmizz.sshj.SSHClient.startSession(SSHClient.java:643)
at org.jclouds.sshj.SshjSshClient$4.create(SshjSshClient.java:447)
at org.jclouds.sshj.SshjSshClient$4.create(SshjSshClient.java:434)
at org.jclouds.sshj.SshjSshClient.acquire(SshjSshClient.java:220)
at
org.jclouds.sshj.SshjSshClient$ExecConnection.create(SshjSshClient.java:477)
at
org.jclouds.sshj.SshjSshClient$ExecConnection.create(SshjSshClient.java:460)
at org.jclouds.sshj.SshjSshClient.acquire(SshjSshClient.java:220)
at org.jclouds.sshj.SshjSshClient.exec(SshjSshClient.java:496)
at
org.jclouds.compute.callables.SudoAwareInitManager.runCommand(SudoAwareInitManager.java:103)
at
org.jclouds.compute.callables.SudoAwareInitManager.runAction(SudoAwareInitManager.java:85)
at
org.jclouds.compute.callables.BlockUntilInitScriptStatusIsZeroThenReturnOutput$1.apply(BlockUntilInitScriptStatusIsZeroThenReturnOutput.java:79)
at
org.jclouds.compute.callables.BlockUntilInitScriptStatusIsZeroThenReturnOutput$1.apply(BlockUntilInitScriptStatusIsZeroThenReturnOutput.java:75)
at
org.jclouds.predicates.RetryablePredicate.apply(RetryablePredicate.java:70)
at
org.jclouds.compute.callables.BlockUntilInitScriptStatusIsZeroThenReturnOutput$3.run(BlockUntilInitScriptStatusIsZeroThenReturnOutput.java:113)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
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:680)
Caused by: java.util.concurrent.TimeoutException: Timeout expired
... 23 more
{noformat}
Do we have something in the sshkey install script that fails on 32bit machines?
> Review automatic image selection
> --------------------------------
>
> Key: WHIRR-410
> URL: https://issues.apache.org/jira/browse/WHIRR-410
> Project: Whirr
> Issue Type: Bug
> Reporter: Andrei Savu
> Fix For: 0.7.0
>
> Attachments: WHIRR-410.patch
>
>
> While I was testing WHIRR-400 I have noticed that the ZooKeeper integration
> tests are failing on aws-ec2 with the automatically selected AMI but they are
> working as expected with the Amazon Linux AMI. The tests are also working as
> expected on cloudservers-us. This makes me think the failure is not related
> to our code changes and we should look for an external factor as the root
> cause.
> As part of this issue we should think about how to improve the automatic AMI
> selection mechanism in order to make it more robust and less likely to fail
> due to AMI upgrades and other external changes.
--
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
