Strange your error reminds me :
https://issues.jenkins-ci.org/browse/JENKINS-33021
Which isn't supposed to be related to IPv4 vs IPv6


On Tue, Dec 6, 2016 at 4:04 PM, Oliver Gondža <[email protected]> wrote:

> I have been utilizing a bunch of machines available over IPv6 only in
> Jenkins using command launcher. I would like to simplify the setup a bit
> delegating large part of the work to ssh-slaves(1.10) plugin but I hit the
> problem with machines connected over IPv6:
>
> ```
> [12/06/16 09:53:15] [SSH] Opening SSH connection to HOSTNAME:22.
> HOSTNAME
> ERROR: Unexpected error in launching a slave. This is probably a bug in
> Jenkins.
> java.lang.IllegalStateException: Connection is not established!
>         at com.trilead.ssh2.Connection.getRemainingAuthMethods(Connecti
> on.java:1030)
>         at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSH
> PublicKeyAuthenticator.getRemainingAuthMethods(Trilea
> dSSHPublicKeyAuthenticator.java:88)
>         at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSH
> PublicKeyAuthenticator.canAuthenticate(TrileadSSHPubl
> icKeyAuthenticator.java:80)
>         at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticato
> r.newInstance(SSHAuthenticator.java:207)
>         at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticato
> r.newInstance(SSHAuthenticator.java:169)
>         at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLaunc
> her.java:1212)
>         at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.
> java:711)
>         at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.
> java:706)
>         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:895)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
> lExecutor.java:918)
>         at java.lang.Thread.run(Thread.java:662)
> ```
>
> I am able to launch agent there using `ssh HOSTNAME bash -l
> agent-launcher-script` so this is not general connectivity issue.
>
> Does someone have similar experience? I suspect trilead ssh just does not
> support it.
>
> Thanks
> --
> oliver
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/jenkinsci-dev/9719d285-9362-d17b-7b2b-a8668bea160a%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
-----
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU--Qc8NENq5DYHeet50aD1HMEqO%3Dd1S5Km%3D1%3D31P40QLSg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to