• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • core
    • Jenkins 2.185, Ubuntu 16.04, OpenJDK 1.8.0, latest plugins (ssh-slaves 1.30)
    • Jenkins 2.186

      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?

       

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

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

          Jens Adam created issue -
          Jens Adam made changes -
          Description Original: {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?
          New: {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').
          Oleg Nenashev made changes -
          Assignee New: Ivan Fernandez Calvo [ ifernandezcalvo ]

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

          Remi Van Goethem added a comment - Same issue here. We have to remain on 2.184 for the time being

          Reiner Wirtz added a comment -

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

          Reiner Wirtz added a comment - Same issue here, We have to go back to Version 2.184

          Ivan Fernandez Calvo added a comment - - edited

          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?

          Ivan Fernandez Calvo added a comment - - edited 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 added a comment - - edited

          Yes, trilead-api-plugin version 1.0.4 is installed

           

          Über Trilead API Plugin 1.0.4

           

          Reiner Wirtz added a comment - - edited Yes, trilead-api-plugin version 1.0.4 is installed   Über Trilead API Plugin 1.0.4  

          Harald Kraemer added a comment - - edited

          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.

          Harald Kraemer added a comment - - edited 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.

          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
          

          Ivan Fernandez Calvo added a comment - 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

          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.

          Ivan Fernandez Calvo added a comment - 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.

            oleg_nenashev Oleg Nenashev
            j_adam Jens Adam
            Votes:
            22 Vote for this issue
            Watchers:
            37 Start watching this issue

              Created:
              Updated:
              Resolved: