[JIRA] (JENKINS-58483) Jenkins 2.185 won't connect to SSH agents

58 views
Skip to first unread message

jens.adam+jenkins@grandcentrix.net (JIRA)

unread,
Jul 14, 2019, 6:30:04 PM7/14/19
to jenkinsc...@googlegroups.com
Jens Adam created an issue
 
Jenkins / Bug JENKINS-58483
Jenkins 2.185 won't connect to SSH agents
Issue Type: Bug Bug
Assignee: Unassigned
Components: core
Created: 2019-07-14 22:29
Environment: Jenkins 2.185, Ubuntu 16.04, OpenJDK 1.8.0, latest plugins (ssh-slaves 1.30)
Priority: Major Major
Reporter: Jens Adam

ERROR: Unexpected error in launching a agent. This is probably a bug in Jenkins.ERROR: Unexpected error in launching a agent. This is probably a bug in Jenkins.java.lang.IllegalArgumentException: Unknown server host key algorithm 'ssh-ed25519' at com.trilead.ssh2.transport.KexManager.checkServerHostkeyAlgorithmsList(KexManager.java:316) at com.trilead.ssh2.Connection.setServerHostKeyAlgorithms(Connection.java:1289) at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:412) at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:406) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)[07/14/19 22:07:00] Launch failed - cleaning up connection[07/14/19 22:07:00] [SSH] Connection closed.

Plugins were updated three days ago and a restart of 2.184 went fine.

Now I just updated to 2.185 and got the quoted "Unknown server host key algorithm 'ssh-ed25519'" messages with all agents (Linux and MacOS) offline.

Probably something related to the recent 'trilead' changes?

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

jens.adam+jenkins@grandcentrix.net (JIRA)

unread,
Jul 14, 2019, 6:37:02 PM7/14/19
to jenkinsc...@googlegroups.com
Jens Adam updated an issue
Change By: Jens Adam
{quote}ERROR: Unexpected error in launching a agent. This is probably a bug in Jenkins.ERROR: Unexpected error in launching a agent. This is probably a bug in Jenkins.java.lang.IllegalArgumentException: Unknown server host key algorithm 'ssh-ed25519' at com.trilead.ssh2.transport.KexManager.checkServerHostkeyAlgorithmsList(KexManager.java:316) at com.trilead.ssh2.Connection.setServerHostKeyAlgorithms(Connection.java:1289) at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:412) at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:406) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)[07/14/19 22:07:00] Launch failed - cleaning up connection[07/14/19 22:07:00] [SSH] Connection closed.
{quote}

Plugins were updated three days ago and a restart of 2.184 went fine.

Now I just updated to 2.185 and got the quoted "Unknown server host key algorithm 'ssh-ed25519'" messages with all agents (Linux and MacOS) offline.

Probably something related to the recent 'trilead' changes?


 

Workaround: Downgrade to previous version ('apt install jenkins=2.184').

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 15, 2019, 2:46:02 AM7/15/19
to jenkinsc...@googlegroups.com
Oleg Nenashev assigned an issue to Ivan Fernandez Calvo
Change By: Oleg Nenashev
Assignee: Ivan Fernandez Calvo

remi.van-goethem@ingenico.com (JIRA)

unread,
Jul 15, 2019, 2:46:03 AM7/15/19
to jenkinsc...@googlegroups.com
Remi Van Goethem commented on Bug JENKINS-58483
 
Re: Jenkins 2.185 won't connect to SSH agents

Same issue here. We have to remain on 2.184 for the time being

reiner.wirtz@ser.de (JIRA)

unread,
Jul 15, 2019, 2:51:02 AM7/15/19
to jenkinsc...@googlegroups.com

Same issue here, We have to go back to Version 2.184

kuisathaverat@gmail.com (JIRA)

unread,
Jul 15, 2019, 4:44:05 AM7/15/19
to jenkinsc...@googlegroups.com
trilead-ssh2-build-217-jenkins-14 is the version provided in Jenkins core 2.184, the version that supports ed25519 is trilead-ssh2-build-217-jenkins-16 that it is included on trilead-api 1.0.4. Could you check if trilead-api 1.0.4 is installed when you use Jenkins core 2.185 ?

kuisathaverat@gmail.com (JIRA)

unread,
Jul 15, 2019, 4:44:05 AM7/15/19
to jenkinsc...@googlegroups.com
 
Re: Jenkins 2.185 won't connect to SSH agents

trilead-ssh2-build-217-jenkins-14 is the version provided in Jenkins core 2.184, the version that supports ed25519 is trilead-ssh2-build-217-jenkins-16 that it is included on trilead-api 1.0.4. Could you check if trilead-api 1.0.4 is installed when you use Jenkins core 2.185

reiner.wirtz@ser.de (JIRA)

unread,
Jul 15, 2019, 5:00:02 AM7/15/19
to jenkinsc...@googlegroups.com

Yes, trilead-api-plugin version 1.0.4 ist installed

 

Über Trilead API Plugin 1.0.4

 

reiner.wirtz@ser.de (JIRA)

unread,
Jul 15, 2019, 5:06:03 AM7/15/19
to jenkinsc...@googlegroups.com
Reiner Wirtz edited a comment on Bug JENKINS-58483
Yes, trilead-api-plugin version 1.0.4 ist is installed

 
h1. Über Trilead API Plugin 1.0.4

 

harald.kraemer@sabio.de (JIRA)

unread,
Jul 15, 2019, 5:16:03 AM7/15/19
to jenkinsc...@googlegroups.com

Hello, I'm currently comparing a 2.185 instance having hits issue and a 2.184 war file. Something that stands out to me:

  • in the 2.184 warfile, I have a trilead-ssh2-build-217-jenkins-14.jar (built 2018)
  • on the 2.185 instance in $install/plugins, I have trilead-api 1.0.4 and trilead-ssh2-build-217-jenkins-16.jar (built 2019)
  • on the 2.185 instance in the warfile, I have trilead-ssh2-build214-jenkins-1.jar (build 2012)

Now I don't know the jenkins classloading here, but the downgrade of the embedded library seems strange.

harald.kraemer@sabio.de (JIRA)

unread,
Jul 15, 2019, 5:17:04 AM7/15/19
to jenkinsc...@googlegroups.com
Harald Kraemer edited a comment on Bug JENKINS-58483
Hello, I'm currently comparing a 2.185 instance having hits issue and a 2.184 war file. Something that stands out to me:
* in the 2.184 warfile, I have a trilead-ssh2-build-217-jenkins-14.jar (built 2018)
* on the 2.185 instance in $install/plugins, I have trilead-api 1.0.4 and trilead-ssh2-build-217-jenkins-16.jar (built 2019)
* on the 2.185 instance in the warfile, I have trilead-ssh2-build214-jenkins-1.jar (build 2012)

Now I don't know the jenkins classloading here, but the downgrade of the embedded library seems strange.
Let me know if I should provide more information.

kuisathaverat@gmail.com (JIRA)

unread,
Jul 15, 2019, 5:28:06 AM7/15/19
to jenkinsc...@googlegroups.com

ok, I've made an update from 2.184 to 2.185 and I found something weird, there are two trilead-ssh libraries and should not, Oleg Nenashev we should mask the library in the Core from the trilead-api plugin

./plugins/trilead-api
./plugins/trilead-api/META-INF/maven/org.jenkins-ci.plugins/trilead-api
./plugins/trilead-api/WEB-INF/lib/trilead-putty-extension-1.2.jar
./plugins/trilead-api/WEB-INF/lib/trilead-ssh2-build-217-jenkins-16.jar
./plugins/trilead-api/WEB-INF/lib/trilead-api.jar
./plugins/trilead-api.jpi
./war/WEB-INF/detached-plugins/trilead-api.hpi
./war/WEB-INF/lib/trilead-putty-extension-1.2.jar
./war/WEB-INF/lib/trilead-ssh2-build214-jenkins-1.jar

kuisathaverat@gmail.com (JIRA)

unread,
Jul 15, 2019, 5:37:02 AM7/15/19
to jenkinsc...@googlegroups.com

I've removed ./war/WEB-INF/lib/trilead-putty-extension-1.2.jar and ./war/WEB-INF/lib/trilead-ssh2-build214-jenkins-1.jar and the issue seems to disappear, so it is a problem related to the duplicated libraries and the class loader.

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 15, 2019, 6:13:02 AM7/15/19
to jenkinsc...@googlegroups.com

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 15, 2019, 6:15:02 AM7/15/19
to jenkinsc...@googlegroups.com
Oleg Nenashev updated an issue
Change By: Oleg Nenashev
Priority: Major Blocker

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 15, 2019, 6:16:03 AM7/15/19
to jenkinsc...@googlegroups.com
Oleg Nenashev commented on Bug JENKINS-58483
 
Re: Jenkins 2.185 won't connect to SSH agents

Looks like Trilead is still being pulled into as a dependnecy, e.g. by SSHD Module or similar components

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 15, 2019, 6:27:05 AM7/15/19
to jenkinsc...@googlegroups.com

troncek@gmail.com (JIRA)

unread,
Jul 15, 2019, 6:28:10 AM7/15/19
to jenkinsc...@googlegroups.com

Same issue here as well using SSH + manually provided key verification strategy. Reverting to 2.184 helps.

tbartley@anonyome.com (JIRA)

unread,
Jul 15, 2019, 6:41:03 AM7/15/19
to jenkinsc...@googlegroups.com

I see a slightly different error signature with inability of 2.185 to contact SSH slave but reverting to 2.184 also resolves the issue.

ssh-slaves plugin version is 1.30.0,

Trilead API plugin version is 1.0.4.

This is the exception I see in the log when launching the agent:

07/15/19 17:05:24] [SSH] Opening SSH connection to 10.194.7.64:22. ERROR: Unexpected error in launching a agent. This is probably a bug in Jenkins. java.lang.NoSuchMethodError: com.trilead.ssh2.Connection.connect(Lcom/trilead/ssh2/ServerHostKeyVerifier;III)Lcom/trilead/ssh2/ConnectionInfo; at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:817) at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:419) at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:406) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 15, 2019, 6:52:02 AM7/15/19
to jenkinsc...@googlegroups.com

I confirm the issue happens in my local build. Looks like it comes from the CLI dependency

 

[INFO] org.jenkins-ci.main:jenkins-core:jar:2.186-SNAPSHOT [INFO] 
+- org.jenkins-ci.plugins.icon-shim:icon-set:jar:1.0.5:compile [INFO] 
+- org.jenkins-ci.main:remoting:jar:3.33:compile [INFO] | \- org.jenkins-ci:constant-pool-scanner:jar:1.2:compile [INFO] +- org.jenkins-ci.main:cli:jar:2.186-SNAPSHOT:compile [INFO] | +- net.i2p.crypto:eddsa:jar:0.3.0:compile [INFO] | \- org.jenkins-ci:trilead-ssh2:jar:build214-jenkins-1:compile

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 15, 2019, 6:57:02 AM7/15/19
to jenkinsc...@googlegroups.com

Oh well, Jenkins core includes CLI https://github.com/jenkinsci/jenkins/blob/jenkins-2.185/core/pom.xml#L58-L62 . Right now I do not have any idea except removing the dependency or excluding the JAR from the dependencies. Both options will unlikely fly well, but I am trying them locally

 

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 15, 2019, 7:24:03 AM7/15/19
to jenkinsc...@googlegroups.com

Created JENKINS-58494 for the CLI dependency removal

rafael.camargo.sp@gmail.com (JIRA)

unread,
Jul 15, 2019, 8:53:03 AM7/15/19
to jenkinsc...@googlegroups.com

rafael.camargo.sp@gmail.com (JIRA)

unread,
Jul 15, 2019, 8:59:03 AM7/15/19
to jenkinsc...@googlegroups.com
Rafael Camargo edited a comment on Bug JENKINS-58483
Same issue here Jenkins 2.185


 

 

 


SSHLauncher\{host='dhp-dev-app-01.sq-cloud.local', port=22, credentialsId='ssh_jenkins', jvmOptions='', javaPath='', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.NonVerifyingKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true}[07/15/19 09:53:34] [SSH] Opening SSH connection to dhp-dev-app-01.sq-cloud.local:22.[07/15/19 09:53:35] [SSH] WARNING: SSH Host Keys are not being verified. Man-in-the-middle attacks may be possible against this connection.ERROR: SSH authentication failedjava.lang.ClassNotFoundException: com.trilead.ssh2.crypto.cipher.BlockCipher at java.net.URLClassLoader.findClass(URLClassLoader.java:382) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:555) at java.lang.ClassLoader.loadClass(ClassLoader.java:357)Caused: java.lang.NoClassDefFoundError: com/trilead/ssh2/crypto/cipher/BlockCipher at com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey.getPrivateKeys(BasicSSHUserPrivateKey.java:174) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.getPrivateKeys(SSHAuthenticator.java:484) at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.doAuthenticate(TrileadSSHPublicKeyAuthenticator.java:107) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:436) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:473) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1213) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:846) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:833) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)[07/15/19 09:53:35] [SSH] Authentication failed.Authentication failed.[07/15/19 09:53:35] Launch failed - cleaning up connection[07/15/19 09:53:35] [SSH] Connection closed.

rafael.camargo.sp@gmail.com (JIRA)

unread,
Jul 15, 2019, 9:01:03 AM7/15/19
to jenkinsc...@googlegroups.com
Rafael Camargo edited a comment on Bug JENKINS-58483
 
{code:java}
Same issue here Jenkins 2.185

 

 

 


SSHLauncher \ {host='dhp-dev-app-01.sq-cloud.local', port=22, credentialsId='ssh_jenkins', jvmOptions='', javaPath='', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.NonVerifyingKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true}[07/15/19 09:53:34] [SSH] Opening SSH connection to dhp-dev-app-01.sq-cloud.local:22.[07/15/19 09:53:35] [SSH] WARNING: SSH Host Keys are not being verified. Man-in-the-middle attacks may be possible against this connection.ERROR: SSH authentication failedjava.lang.ClassNotFoundException: com.trilead.ssh2.crypto.cipher.BlockCipher at java.net.URLClassLoader.findClass(URLClassLoader.java:382) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:555) at java.lang.ClassLoader.loadClass(ClassLoader.java:357)Caused: java.lang.NoClassDefFoundError: com/trilead/ssh2/crypto/cipher/BlockCipher at com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey.getPrivateKeys(BasicSSHUserPrivateKey.java:174) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.getPrivateKeys(SSHAuthenticator.java:484) at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.doAuthenticate(TrileadSSHPublicKeyAuthenticator.java:107) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:436) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:473) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1213) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:846) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:833) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)[07/15/19 09:53:35] [SSH] Authentication failed.Authentication failed.[07/15/19 09:53:35] Launch failed - cleaning up connection[07/15/19 09:53:35] [SSH] Connection closed.

{code}
 

rmnobarra@gmail.com (JIRA)

unread,
Jul 15, 2019, 9:04:04 AM7/15/19
to jenkinsc...@googlegroups.com

Same issue with Jenkins 2.185
 
SSHLauncher

{host='dhp-dev-app-01.sq-cloud.local', port=22, credentialsId='ssh_jenkins', jvmOptions='', javaPath='', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.NonVerifyingKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true}

[07/15/19 09:53:34] [SSH] Opening SSH connection to dhp-dev-app-01.sq-cloud.local:22.[07/15/19 09:53:35] [SSH] WARNING: SSH Host Keys are not being verified. Man-in-the-middle attacks may be possible against this connection.ERROR: SSH authentication failedjava.lang.ClassNotFoundException: com.trilead.ssh2.crypto.cipher.BlockCipher at java.net.URLClassLoader.findClass(URLClassLoader.java:382) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:555) at java.lang.ClassLoader.loadClass(ClassLoader.java:357)Caused: java.lang.NoClassDefFoundError: com/trilead/ssh2/crypto/cipher/BlockCipher at com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey.getPrivateKeys(BasicSSHUserPrivateKey.java:174) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.getPrivateKeys(SSHAuthenticator.java:484) at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.doAuthenticate(TrileadSSHPublicKeyAuthenticator.java:107) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:436) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:473) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1213) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:846) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:833) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)[07/15/19 09:53:35] [SSH] Authentication failed.Authentication failed.[07/15/19 09:53:35] Launch failed - cleaning up connection[07/15/19 09:53:35] [SSH] Connection closed.

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 15, 2019, 9:06:03 AM7/15/19
to jenkinsc...@googlegroups.com

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 15, 2019, 10:55:04 AM7/15/19
to jenkinsc...@googlegroups.com
Oleg Nenashev assigned an issue to Oleg Nenashev
 
Change By: Oleg Nenashev
Assignee: Ivan Fernandez Calvo Oleg Nenashev

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 15, 2019, 10:55:06 AM7/15/19
to jenkinsc...@googlegroups.com
Oleg Nenashev started work on Bug JENKINS-58483
 
Change By: Oleg Nenashev
Status: Open In Progress

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 15, 2019, 8:43:03 PM7/15/19
to jenkinsc...@googlegroups.com

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 15, 2019, 8:44:04 PM7/15/19
to jenkinsc...@googlegroups.com
 
Re: Jenkins 2.185 won't connect to SSH agents

Apparently there was a regression in SSH CLI Auth Module which was not discovered in reviews. https://github.com/jenkinsci/ssh-cli-auth-module/pull/14 should fix it

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 16, 2019, 4:29:03 AM7/16/19
to jenkinsc...@googlegroups.com

Whomever needs a test build of the fix, it is here: https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.186-rc28479.a2d1d0c725fe/ . Downgrade is still recommended for production use. I hope we will rollout an out-of-order weekly release by EoD tomorrow, see https://groups.google.com/forum/#!topic/jenkinsci-advisories/lWw746kv4Kg 

cleclerc@cloudbees.com (JIRA)

unread,
Jul 16, 2019, 8:26:04 AM7/16/19
to jenkinsc...@googlegroups.com
Cyrille Le Clerc updated an issue
 
Change By: Cyrille Le Clerc
{ quote noformat }
ERROR: Unexpected error in launching a agent. This is probably a bug in Jenkins.ERROR: Unexpected error in launching a agent. This is probably a bug in Jenkins.java.lang.IllegalArgumentException: Unknown server host key algorithm 'ssh-ed25519'
at com.trilead.ssh2.transport.KexManager.checkServerHostkeyAlgorithmsList(KexManager.java:316)
at com.trilead.ssh2.Connection.setServerHostKeyAlgorithms(Connection.java:1289)
at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:412)
at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:406)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)[07/14/19 22:07:00] Launch failed - cleaning up connection[07/14/19 22:07:00] [SSH] Connection closed.
{
quote noformat }

Plugins were updated three days ago and a restart of 2.184 went fine.

Now I just updated to 2.185 and got the quoted "Unknown server host key algorithm 'ssh-ed25519'" messages with all agents (Linux and MacOS) offline.

Probably something related to the recent 'trilead' changes?

 

Workaround: Downgrade to previous version ('apt install jenkins=2.184').

cleclerc@cloudbees.com (JIRA)

unread,
Jul 16, 2019, 8:26:07 AM7/16/19
to jenkinsc...@googlegroups.com
Cyrille Le Clerc updated an issue
{noformat}

ERROR: Unexpected error in launching a agent. This is probably a bug in Jenkins.ERROR: Unexpected error in launching a agent. This is probably a bug in Jenkins.
java.lang.IllegalArgumentException: Unknown server host key algorithm 'ssh-ed25519'
at com.trilead.ssh2.transport.KexManager.checkServerHostkeyAlgorithmsList(KexManager.java:316)
at com.trilead.ssh2.Connection.setServerHostKeyAlgorithms(Connection.java:1289)
at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:412)
at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:406)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)[07/14/19 22:07:00] Launch failed - cleaning up connection[07/14/19 22:07:00] [SSH] Connection closed.
{noformat}


Plugins were updated three days ago and a restart of 2.184 went fine.

Now I just updated to 2.185 and got the quoted "Unknown server host key algorithm 'ssh-ed25519'" messages with all agents (Linux and MacOS) offline.

Probably something related to the recent 'trilead' changes?

 

Workaround: Downgrade to previous version ('apt install jenkins=2.184').

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 17, 2019, 4:39:05 AM7/17/19
to jenkinsc...@googlegroups.com
 

To be released in 2.186 today, unless something goes really wrong

Change By: Oleg Nenashev
Status: In Review Fixed but Unreleased
Resolution: Fixed

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 17, 2019, 11:16:28 AM7/17/19
to jenkinsc...@googlegroups.com
Change By: Oleg Nenashev
Status: Fixed but Unreleased Resolved
Released As: Jenkins 2.186

bharatbhatia18@gmail.com (JIRA)

unread,
Jul 18, 2019, 9:13:03 AM7/18/19
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages