[JIRA] [ec2-plugin] (JENKINS-34100) Launch of cloud slave fails with "No route to host"

[tyler@monkeypox.org (JIRA)]

R. Tyler Croy moved an issue

Jenkins / JENKINS-34100 Launch of cloud slave fails with "No route to host" Change By: R. Tyler Croy Project: Infrastructure Jenkins Key: INFRA JENKINS - 629 34100 Workflow: classic default workflow JNJira Component/s: ec2-plugin Component/s: core Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[tyler@monkeypox.org (JIRA)]

R. Tyler Croy updated an issue

Jenkins / JENKINS-34100 Launch of cloud slave fails with "No route to host"

Change By: R. Tyler Croy

Component/s: openstack-cloud-plugin Component/s: ec2-plugin

Add Comment

[tyler@monkeypox.org (JIRA)]

R. Tyler Croy assigned an issue to Marat Mavlyutov

Jenkins / JENKINS-34100 Launch of cloud slave fails with "No route to host"

Change By: R. Tyler Croy

Assignee: R. Tyler Croy Marat Mavlyutov

Add Comment

[ogondza@gmail.com (JIRA)]

Oliver Gondža assigned an issue to Oliver Gondža

Jenkins / JENKINS-34100 Launch of cloud slave fails with "No route to host"

Change By: Oliver Gondža Assignee: Marat Mavlyutov Oliver Gondža

Add Comment

[ogondza@gmail.com (JIRA)]

Oliver Gondža commented on JENKINS-34100

Re: Launch of cloud slave fails with "No route to host" Hmm, there ware some changes to the code in 2.1 where I expected to improve the situation. Please have a look into the service log for messages involving the slave name. Also, what is in the $JENKINS_HOME/logs/slaves/$SLAVE_NAME? Usually, there is couple of logs tracking how several instances of "no route to host" / "connection refused" turned into successful connection.

Add Comment

[peter.hansen@myloc.de (JIRA)]

Peter Hansen edited a comment on JENKINS-34100

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

I experience the same problem here. The logfile says:  {{ [05/20/16 13:01:45] [SSH] Opening SSH connection to 192.168.1.36:22. No route to host ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins. ha:AAAAWB+LCAAAAAAAAP9b85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWAAAAA=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:212) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:172) 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) [05/20/16 13:01:48] Launch failed - cleaning up connection [05/20/16 13:01:48] [SSH] Connection closed. }} When manually launching the agent using the Jenkins UI after some minutes the problem does not occur.  Is there any workaround? How to automatically reschedule the start of the agent?

Add Comment

[peter.hansen@myloc.de (JIRA)]

Peter Hansen commented on JENKINS-34100

[bromister@gmail.com (JIRA)]

Roman Babyuk commented on JENKINS-34100

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

I am expecting the same issue voting for resolving Thanks, Roman

Add Comment

[peter.hansen@myloc.de (JIRA)]

Peter Hansen commented on JENKINS-34100

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

Hey Roman, This issue refers to the same problem as https://github.com/jenkinsci/openstack-cloud-plugin/issues/73.

Add Comment

[bromister@gmail.com (JIRA)]

Roman Babyuk commented on JENKINS-34100

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

Peter Hansen Thx! voted there too

Add Comment

[ogondza@gmail.com (JIRA)]

Oliver Gondža commented on JENKINS-34100

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

Identified the root cause in ssh-slaves-plugin. Will propose a fix there.

Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[ogondza@gmail.com (JIRA)]

Oliver Gondža commented on JENKINS-34100

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

Fix proposed, no change on openstack-cloud should be required so update to fixed ssh-slaves will be sufficient once released.

Add Comment

[ogondza@gmail.com (JIRA)]

Oliver Gondža started work on JENKINS-34100

Change By: Oliver Gondža Status: Open In Progress

Add Comment

[scm_issue_link@java.net (JIRA)]

SCM/JIRA link daemon commented on JENKINS-34100

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

Code changed in jenkins User: Oliver Gondža Path: src/main/java/hudson/plugins/sshslaves/SSHLauncher.java http://jenkins-ci.org/commit/ssh-slaves-plugin/44d7e2f9b1c768c52002e06b3ebecf5399f81cdb Log: [FIXED JENKINS-26379][FIXED JENKINS-41163]JENKINS-34100 Do not swallow IOException in case it is not recoverable.

Add Comment

[ogondza@gmail.com (JIRA)]

Oliver Gondža resolved as Fixed

Fixed in 2.18. There is a similar problem that still exists[1], connection is not retried in case of auth failure. [1] https://github.com/jenkinsci/openstack-cloud-plugin/issues/137

Jenkins / JENKINS-34100

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

Change By: Oliver Gondža Status: In Progress Resolved Resolution: Fixed

Add Comment