[JIRA] (JENKINS-60535) Getting IOException when Jenkins is trying to connect to Slaves in Azure Cloud

19 views
Skip to first unread message

adugar@apttus.com (JIRA)

unread,
Dec 19, 2019, 12:52:03 AM12/19/19
to jenkinsc...@googlegroups.com
anil dugar created an issue
 
Jenkins / Bug JENKINS-60535
Getting IOException when Jenkins is trying to connect to Slaves in Azure Cloud
Issue Type: Bug Bug
Assignee: Azure DevOps
Attachments: azourecloudexception.png, EOFException in Job, Issue discussed with microsoft.txt, list of all failures.png
Components: azure-vm-agents-plugin
Created: 2019-12-19 05:51
Environment: Jenkins Version : 2.190.1
Priority: Major Major
Reporter: anil dugar

While provisioning from jenkins master we are getting exception: AzureCloudException java.io.IOException: Agent failed to connect

And below is the exception that we are getting :

AzureCloudException

java.io.IOException: Agent failed to connect, even though the launcher didn't report it. See the log output for details.
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:321)
Caused: java.util.concurrent.ExecutionException
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at com.microsoft.azure.vmagent.AzureVMCloud$2.call(AzureVMCloud.java:856)
Caused: com.microsoft.azure.vmagent.exceptions.AzureCloudException
at com.microsoft.azure.vmagent.exceptions.AzureCloudException.create(AzureCloudException.java:54)
at com.microsoft.azure.vmagent.exceptions.AzureCloudException.create(AzureCloudException.java:33)
at com.microsoft.azure.vmagent.AzureVMCloud$2.call(AzureVMCloud.java:885)
at com.microsoft.azure.vmagent.AzureVMCloud$2.call(AzureVMCloud.java:808)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)
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)

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

jieshe@microsoft.com (JIRA)

unread,
Dec 19, 2019, 1:32:03 AM12/19/19
to jenkinsc...@googlegroups.com

jieshe@microsoft.com (JIRA)

unread,
Dec 19, 2019, 3:06:04 AM12/19/19
to jenkinsc...@googlegroups.com

adugar@apttus.com (JIRA)

unread,
Dec 19, 2019, 6:04:05 AM12/19/19
to jenkinsc...@googlegroups.com

adugar@apttus.com (JIRA)

unread,
Dec 19, 2019, 6:04:05 AM12/19/19
to jenkinsc...@googlegroups.com

jieshe@microsoft.com (JIRA)

unread,
Dec 20, 2019, 3:33:03 AM12/20/19
to jenkinsc...@googlegroups.com
Jie Shen commented on Bug JENKINS-60535

According to the log, it seems to be caused by firewall or something like that. Do you have ever tried other windows images, such as the default one?

adugar@apttus.com (JIRA)

unread,
Jan 10, 2020, 2:17:03 AM1/10/20
to jenkinsc...@googlegroups.com

Sometimes the jobs fail and sometimes they succeed, which means the issue is reported intermittently, so i dont think firewall would be an issue. and if at firewall would be causing the problem, the jobs should fail everytime which is not the case.

jieshe@microsoft.com (JIRA)

unread,
Jan 14, 2020, 7:08:07 AM1/14/20
to jenkinsc...@googlegroups.com
Jie Shen commented on Bug JENKINS-60535

anil dugar Temporarily the logic for SSH launch will only try once. If it fails to connect, it will directly throw exceptions like what you get. So have you tried the JNLP launch method? And I will check whether retry logic will make things better for SSH.

jieshe@microsoft.com (JIRA)

unread,
Feb 10, 2020, 1:30:03 AM2/10/20
to jenkinsc...@googlegroups.com
Jie Shen commented on Bug JENKINS-60535

Version 1.4.0 has been released with the SSH connect retry feature.

adugar@apttus.com (JIRA)

unread,
Feb 13, 2020, 2:22:03 AM2/13/20
to jenkinsc...@googlegroups.com

Thanks Jie, we are also working on an optimistic solution of having a retry logic, hopefully that will work and also we will have a loot at the above mentioned feature.

Reply all
Reply to author
Forward
0 new messages