You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jclouds.apache.org by Andrew Phillips <no...@github.com> on 2014/02/03 17:37:58 UTC
[jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
See https://issues.apache.org/jira/browse/JCLOUDS-448
You can merge this Pull Request by running:
git pull https://github.com/jclouds/jclouds up-sshj
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds/pull/274
-- Commit Summary --
* Upgrading sshj 0.8.1 -> 0.9.0
-- File Changes --
M drivers/sshj/pom.xml (2)
-- Patch Links --
https://github.com/jclouds/jclouds/pull/274.patch
https://github.com/jclouds/jclouds/pull/274.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by Andrew Phillips <no...@github.com>.
> Tomorrow I'll run again the tests with the older sshj + bouncycastle versions so we can compare
> and make a proper decision if this should be merged or not. Sounds good?
Works for me! There's no _huge_ rush on this PR, after all.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34142046
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by Andrew Phillips <no...@github.com>.
> but it turns that sshj 0.9.0 already brings the bcpkix dep, so I'm pretty confident we'll see the same
> results.
Good to hear...gearing up for the merges, then ;-)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34115641
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by Ignasi Barrera <no...@github.com>.
@demobox Running them right now, but it turns that sshj 0.9.0 already brings the bcpkix dep, so I'm pretty confident we'll see the same results. The dependency:tree on the sshj driver shows:
```bash
[INFO] +- net.schmizz:sshj:jar:0.9.0:compile
[INFO] | \- org.bouncycastle:bcpkix-jdk15on:jar:1.49:compile
```
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34114685
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by Andrew Phillips <no...@github.com>.
> Shame on me.
Certainly not! Thanks for working through to try to figure out what was going on. And let's see whether upgrading the dep helps at all ;-)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34087648
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-java-7-pull-requests #1027](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1027/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34003289
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by Ignasi Barrera <no...@github.com>.
I've just run the live tests one more time and now one test is failing always at the same point:
The `testAScriptExecutionAfterBootWithBasicTemplate ` is now failing [here](https://github.com/jclouds/jclouds/blob/master/compute/src/test/java/org/jclouds/compute/internal/BaseComputeServiceLiveTest.java#L309) (the method is disabled as a test but it is called internally). To be more precise, the failure happens here: https://github.com/jclouds/jclouds/blob/master/compute/src/main/java/org/jclouds/compute/callables/SudoAwareInitManager.java#L78
There have not been changes in the code of the provider, and it only fails at that point, after modifying the node credentials and trying to cancel the task. I'm not sure where the issue can be, but the live tests perform many other node access, generate SSH keys, etc, so I'm pretty confident the bouncycastle dependency shouldn't be a problem (but on the other hand, the code in the provider hasn't changed).
If you are ok with this, I think it is safe to merge this and the DigitalOcean pull requests (all live tests except that concrete bit are passing and the runscript stuff, which uses the sshj driver, is tested in many ways), and investigate the issue later, as it may take time to isolate.
Do you prefer to merge or prefer to wait?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34116447
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-pull-requests #558](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/558/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34003328
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by Andrew Phillips <no...@github.com>.
> jclouds » jclouds #798 FAILURE
Doh! Stupid compilation failure. Hopefully fixed with the upcoming commit.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-33979888
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-pull-requests #564](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/564/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34108580
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-pull-requests #556](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/556/) FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-33983343
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by Ignasi Barrera <no...@github.com>.
After some research it seems that adding [bcpkix-jdk15on](http://search.maven.org/#artifactdetails%7Corg.bouncycastle%7Cbcpkix-jdk15on%7C1.49%7Cjar) to the bouncycastle driver should fix this.
```xml
<dependency>
<groupId>org.bouncycastle</groupId>
<artifactId>bcpkix-jdk15on</artifactId>
<version>1.49</version>
</dependency>
```
Will try now and post the results here!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34061417
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by Andrew Phillips <no...@github.com>.
> I've just run the live tests one more time and now one test is failing always at the same point:
Hm. That does look like something related to the SSH driver, though. Do you know if that call is made _successfully_ anywhere in the live tests?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34117381
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by Andrew Phillips <no...@github.com>.
> WDYT?
Let's try it and see what happens ;-) I think we should figure out at some point what is going on, since getting stuck on an old version of SSHJ doesn't seem like a great idea. But for now this seems like a good way forward. I'll also ask Andrea to test with this combination.
Thanks again for the thorough testing!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34146746
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by Ignasi Barrera <no...@github.com>.
Executed again the live tests and adding the following dependency to the bouncycastle driver seems to fix the issue:
```xml
<dependency>
<groupId>org.bouncycastle</groupId>
<artifactId>bcpkix-jdk15on</artifactId>
<version>1.49</version>
<exclusions>
<exclusion>
<groupId>org.bouncycastle</groupId>
<artifactId>bcprov-jdk15on</artifactId>
</exclusion>
</exclusions>
</dependency>
```
@demobox mind updating this PR and the related ones?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34073349
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by Andrew Phillips <no...@github.com>.
> @demobox mind updating this PR and the related ones?
No problem, will do. Wondering what changed in Bouncy...seems like they've split up stuff quite a lot. Thanks for investigating! And a lesson to learn about commits going in that cause things to fail - need to see how to run live tests more regularly, I guess!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34077323
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-java-7-pull-requests #1035](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1035/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34108530
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-java-7-pull-requests #1024](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1024/) FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-33983272
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-java-7-pull-requests #1019](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1019/) FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-33974392
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by CloudBees pull request builder plugin <no...@github.com>.
[jclouds-pull-requests #550](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/550/) FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-33974449
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by Ignasi Barrera <no...@github.com>.
Run the ComputeServiceLive tests against DigitalOcean and there were failures due to the new Bouncycastle dependency.
The following are the dependencies for the project:
```bash
--- maven-dependency-plugin:2.1:tree (default-cli) @ digitalocean ---
[INFO] org.apache.jclouds.labs:digitalocean:bundle:1.8.0-SNAPSHOT
[INFO] +- org.apache.jclouds:jclouds-compute:jar:1.8.0-SNAPSHOT:compile
[INFO] | +- org.apache.jclouds:jclouds-scriptbuilder:jar:1.8.0-SNAPSHOT:compile
[INFO] | \- org.apache.jclouds:jclouds-core:jar:1.8.0-SNAPSHOT:compile
[INFO] | +- javax.ws.rs:jsr311-api:jar:1.1.1:compile
[INFO] | +- com.google.inject.extensions:guice-assistedinject:jar:3.0:compile
[INFO] | +- com.google.inject:guice:jar:3.0:compile
[INFO] | | \- aopalliance:aopalliance:jar:1.0:compile
[INFO] | +- org.99soft.guice:rocoto:jar:6.2:compile
[INFO] | +- javax.inject:javax.inject:jar:1:compile
[INFO] | +- javax.annotation:jsr250-api:jar:1.0:compile
[INFO] | +- com.google.code.gson:gson:jar:2.2.4:compile
[INFO] | \- com.google.guava:guava:jar:16.0:compile
[INFO] +- org.apache.jclouds.driver:jclouds-sshj:jar:1.8.0-SNAPSHOT:test
[INFO] | +- org.apache.jclouds.driver:jclouds-slf4j:jar:1.8.0-SNAPSHOT:test
[INFO] | | \- org.slf4j:slf4j-api:jar:1.7.2:test
[INFO] | +- org.apache.jclouds.driver:jclouds-bouncycastle:jar:1.8.0-SNAPSHOT:test
[INFO] | | \- org.bouncycastle:bcprov-ext-jdk15on:jar:1.49:test
[INFO] | \- net.schmizz:sshj:jar:0.8.1:test
[INFO] +- org.apache.jclouds:jclouds-core:test-jar:tests:1.8.0-SNAPSHOT:test
[INFO] +- org.apache.jclouds:jclouds-compute:test-jar:tests:1.8.0-SNAPSHOT:test
[INFO] +- com.squareup.okhttp:mockwebserver:jar:1.3.0:test
[INFO] | \- com.squareup.okhttp:okhttp-protocols:jar:1.3.0:test
[INFO] +- org.testng:testng:jar:6.8:test
[INFO] | +- org.beanshell:bsh:jar:2.0b4:test
[INFO] | +- com.beust:jcommander:jar:1.27:test
[INFO] | \- org.yaml:snakeyaml:jar:1.6:test
[INFO] +- org.easymock:easymockclassextension:jar:3.1:test
[INFO] | \- org.easymock:easymock:jar:3.1:test
[INFO] | +- cglib:cglib-nodep:jar:2.2.2:test
[INFO] | \- org.objenesis:objenesis:jar:1.2:test
[INFO] +- xmlunit:xmlunit:jar:1.3:test
[INFO] +- org.clojure:clojure:jar:1.3.0:compile
[INFO] +- org.clojure:tools.logging:jar:0.2.3:compile
[INFO] \- org.clojure:core.incubator:jar:0.1.0:compile
```
As you can see the new Bouncycastle dependency is present. The tests, though, present the following failures:
```bash
java.lang.NoClassDefFoundError: org/bouncycastle/openssl/EncryptionException
at org.jclouds.sshj.SSHClientConnection.create(SSHClientConnection.java:140)
at org.jclouds.sshj.SSHClientConnection.create(SSHClientConnection.java:38)
at org.jclouds.sshj.SshjSshClient.acquire(SshjSshClient.java:191)
at org.jclouds.sshj.SshjSshClient.connect(SshjSshClient.java:221)
at org.jclouds.compute.callables.RunScriptOnNodeAsInitScriptUsingSsh.call(RunScriptOnNodeAsInitScriptUsingSsh.java:76)
at org.jclouds.compute.internal.BaseComputeService.runScriptOnNode(BaseComputeService.java:615)
at org.jclouds.compute.internal.BaseComputeServiceLiveTest.createAndRunAServiceInGroup(BaseComputeServiceLiveTest.java:717)
at org.jclouds.compute.internal.BaseComputeServiceLiveTest.testCreateAndRunAService(BaseComputeServiceLiveTest.java:690)
...
Caused by: java.lang.ClassNotFoundException: org.bouncycastle.openssl.EncryptionException
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
... 29 more
```
It seems that there is some dependency we should add too to the `jclouds-sshj` driver
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34048337
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by Andrew Phillips <no...@github.com>.
> is now failing here
Oh, er, and what's the error? ;-)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34117694
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by BuildHive <no...@github.com>.
[jclouds » jclouds #798](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/798/) FAILURE
Looks like there's a problem with this pull request
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-33978624
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by Andrew Phillips <no...@github.com>.
> jclouds-pull-requests #556 FAILURE
Now a duplicate dep introduced by the new sshj version. For next time: running `mvn clean verify` rather than `mvn clean test` locally is probably a good idea ;-)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-33998023
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by Ignasi Barrera <no...@github.com>.
>I think we should figure out at some point what is going on, since getting stuck on an old version of SSHJ doesn't seem like a great idea
Agree. I've opened [JCLOUDS-451](https://issues.apache.org/jira/browse/JCLOUDS-451) to investigate this. Meanwhile, with this approach we should be able to use BC 1.49 and while keeping the ComptueServiceLiveTests passing.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34147315
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by Andrew Phillips <no...@github.com>.
PR builders looking OK. Waiting on your tests now, @nacx! ;-)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34110710
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by Andrew Phillips <no...@github.com>.
@nacx: Actually, I think you may be seeing the same issue as Andrea was in https://github.com/jclouds/jclouds/pull/273. Could you try what he did - exclude sshj (you have the old 0.8.1 version in your dep list) and try again with the 0.9.0 version?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34085676
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by Ignasi Barrera <no...@github.com>.
@demobox, I've run the live tests again with different combinations of sshj and bouncycastle:
* [x] **sshj 0.8.1 / bouncycastle 1.46**
testAScriptExecutionAfterBootWithBasicTemplate(org.jclouds.digitalocean.compute.DigitalOceanComputeServiceLiveTest) _succeeded_
* [x] **sshj 0.8.1 / bouncycastle 1.49**
testAScriptExecutionAfterBootWithBasicTemplate(org.jclouds.digitalocean.compute.DigitalOceanComputeServiceLiveTest) _succeeded_
* [x] **sshj 0.9.0 / bouncycastle 1.49**
testAScriptExecutionAfterBootWithBasicTemplate(org.jclouds.digitalocean.compute.DigitalOceanComputeServiceLiveTest) _failed_
* [ ] **sshj 0.9.0 / bouncycastle 1.46**
Haven't tested it, but I don't think it is a good idea as sshj 0.9.0 dends on BC 1.49 and forcing it to an earlier version does not seema good idea.
So it seems that sshj 0.8.1 works with both, BC 1.46 and 1.49, but sshj 0.9.0 presents the connection issue. With this results in mind, I'd suggest **not** upgrading the sshj dependency but configuring the following in the *jclouds-sshj* driver to make sure it uses BC 1.49:
```xml
<dependency>
<groupId>org.bouncycastle</groupId>
<artifactId>bcpkix-jdk15on</artifactId>
<version>1.49</version>
<exclusions>
<exclusion>
<groupId>org.bouncycastle</groupId>
<artifactId>bcprov-jdk15on</artifactId>
</exclusion>
</exclusions>
</dependency>
```
WDYT?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34146391
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by Ignasi Barrera <no...@github.com>.
Shame on me. I double checked that, but when running the live tests with the depedency change already made, so now I don't know if it is actually needed with the new ssh.
Will run the tests again with the new sshj and without the dependency later today, and post the results here. Thanks for spotting that!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34086389
Re: [jclouds] Upgrading sshj 0.8.1 -> 0.9.0 (#274)
Posted by Ignasi Barrera <no...@github.com>.
This is the complete stacktrace for the failed test:
```bash
testAScriptExecutionAfterBootWithBasicTemplate(org.jclouds.digitalocean.compute.DigitalOceanComputeServiceLiveTest) Time elapsed: 214.337 sec <<< FAILURE!
org.jclouds.rest.AuthorizationException: (foo:rsa[fingerprint(1b:28:a6:e9:82:75:3f:3b:8e:1f:aa:b7:35:0f:1c:81),sha1(80:94:6f:57:50:5d:10:d4:e6:5f:0e:5f:ea:1e:17:ac:22:c7:56:01)]@192.241.153.27:22) (foo:rsa[fingerprint(1b:28:a6:e9:82:75:3f:3b:8e:1f:aa:b7:35:0f:1c:81),sha1(80:94:6f:57:50:5d:10:d4:e6:5f:0e:5f:ea:1e:17:ac:22:c7:56:01)]@192.241.153.27:22) error acquiring {hostAndPort=192.241.153.27:22, loginUser=foo, ssh=1277971554, connectTimeout=60000, sessionTimeout=60000} (not retryable): Exhausted available authentication methods
at org.jclouds.sshj.SshjSshClient.propagate(SshjSshClient.java:380)
at org.jclouds.sshj.SshjSshClient.acquire(SshjSshClient.java:211)
at org.jclouds.sshj.SshjSshClient.connect(SshjSshClient.java:221)
at org.jclouds.compute.callables.SudoAwareInitManager.refreshAndRunAction(SudoAwareInitManager.java:78)
at org.jclouds.compute.callables.BlockUntilInitScriptStatusIsZeroThenReturnOutput.interruptTask(BlockUntilInitScriptStatusIsZeroThenReturnOutput.java:161)
at com.google.common.util.concurrent.AbstractFuture.cancel(AbstractFuture.java:136)
at org.jclouds.compute.internal.BaseComputeServiceLiveTest.weCanCancelTasks(BaseComputeServiceLiveTest.java:309)
at org.jclouds.compute.internal.BaseComputeServiceLiveTest.testAScriptExecutionAfterBootWithBasicTemplate(BaseComputeServiceLiveTest.java:266)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
at org.testng.TestRunner.privateRun(TestRunner.java:767)
at org.testng.TestRunner.run(TestRunner.java:617)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.access$000(SuiteRunner.java:37)
at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368)
at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
Caused by: net.schmizz.sshj.userauth.UserAuthException: Exhausted available authentication methods
at net.schmizz.sshj.SSHClient.auth(SSHClient.java:217)
at net.schmizz.sshj.SSHClient.authPublickey(SSHClient.java:316)
at net.schmizz.sshj.SSHClient.authPublickey(SSHClient.java:335)
at org.jclouds.sshj.SSHClientConnection.create(SSHClientConnection.java:142)
at org.jclouds.sshj.SSHClientConnection.create(SSHClientConnection.java:38)
at org.jclouds.sshj.SshjSshClient.acquire(SshjSshClient.java:191)
... 26 more
Caused by: net.schmizz.sshj.userauth.UserAuthException: Timeout expired
at net.schmizz.sshj.userauth.UserAuthException$1.chain(UserAuthException.java:33)
at net.schmizz.sshj.userauth.UserAuthException$1.chain(UserAuthException.java:26)
at net.schmizz.concurrent.Promise.retrieve(Promise.java:139)
at net.schmizz.sshj.userauth.UserAuthImpl.authenticate(UserAuthImpl.java:69)
at net.schmizz.sshj.SSHClient.auth(SSHClient.java:211)
... 31 more
Caused by: java.util.concurrent.TimeoutException: Timeout expired
... 34 more
Caused by: net.schmizz.sshj.userauth.UserAuthException: Exhausted available authentication methods
at net.schmizz.sshj.SSHClient.auth(SSHClient.java:217)
at net.schmizz.sshj.SSHClient.authPublickey(SSHClient.java:316)
at net.schmizz.sshj.SSHClient.authPublickey(SSHClient.java:335)
at org.jclouds.sshj.SSHClientConnection.create(SSHClientConnection.java:142)
at org.jclouds.sshj.SSHClientConnection.create(SSHClientConnection.java:38)
at org.jclouds.sshj.SshjSshClient.acquire(SshjSshClient.java:191)
... 26 more
Caused by: net.schmizz.sshj.userauth.UserAuthException: Timeout expired
at net.schmizz.sshj.userauth.UserAuthException$1.chain(UserAuthException.java:33)
at net.schmizz.sshj.userauth.UserAuthException$1.chain(UserAuthException.java:26)
at net.schmizz.concurrent.Promise.retrieve(Promise.java:139)
at net.schmizz.sshj.userauth.UserAuthImpl.authenticate(UserAuthImpl.java:69)
at net.schmizz.sshj.SSHClient.auth(SSHClient.java:211)
... 31 more
Caused by: java.util.concurrent.TimeoutException: Timeout expired
... 34 more
```
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/274#issuecomment-34119715