Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-34100

Launch of cloud slave fails with "No route to host"

      When launching a cloud slave, the VM is created and starts booting, but before it is available, Jenkins fails with this error.

      [04/05/16 17:09:02] [SSH] Opening SSH connection to 10.0.2.39:22.
      No route to host
      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(Connection.java:1030)
      at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.getRemainingAuthMethods(TrileadSSHPublicKeyAuthenticator.java:88)
      at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.canAuthenticate(TrileadSSHPublicKeyAuthenticator.java:80)
      at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:207)
      at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:169)
      at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.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.run(FutureTask.java:266)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      at java.lang.Thread.run(Thread.java:745)
      [04/05/16 17:09:05] Launch failed - cleaning up connection
      [04/05/16 17:09:05] [SSH] Connection closed.

      If I wait about a minute and click 'Launch Slave Agent' it works fine.

      The solution, it seems, would be to permit retries on a 'No route to host' error, rather than failing immediately. Also, this worked fine a few versions back. I don't know exactly when it broke.

          [JENKINS-34100] Launch of cloud slave fails with "No route to host"

          Adam Mendlik created issue -
          R. Tyler Croy made changes -
          Component/s New: ec2-plugin [ 15625 ]
          Component/s Original: core [ 21134 ]
          Key Original: INFRA-629 New: JENKINS-34100
          Workflow Original: classic default workflow [ 170129 ] New: JNJira [ 170129 ]
          Project Original: Infrastructure [ 10301 ] New: Jenkins [ 10172 ]
          R. Tyler Croy made changes -
          Component/s New: openstack-cloud-plugin [ 20631 ]
          Component/s Original: ec2-plugin [ 15625 ]
          R. Tyler Croy made changes -
          Assignee Original: R. Tyler Croy [ rtyler ] New: Marat Mavlyutov [ mavlyutov ]
          Oliver Gondža made changes -
          Assignee Original: Marat Mavlyutov [ mavlyutov ] New: Oliver Gondža [ olivergondza ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 170130 ] New: JNJira + In-Review [ 183775 ]
          Oliver Gondža made changes -
          Link New: This issue depends on JENKINS-41163 [ JENKINS-41163 ]
          Oliver Gondža made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Oliver Gondža made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]

            olivergondza Oliver Gondža
            amendlik Adam Mendlik
            Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: