AzureVMAgentSSHLauncher: getRemoteSession: Got exception while connecting to remote host ubuntu-jenkinsinfraf4fce1.eastus2.cloudapp.azure.com:22 java.net.UnknownHostException: ubuntu-jenkinsinfraf4fce1.eastus2.cloudapp.azure.com at java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:220) at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:403) at java.base/java.net.Socket.connect(Socket.java:591) at java.base/java.net.Socket.connect(Socket.java:540) at java.base/java.net.Socket.<init>(Socket.java:436) at java.base/java.net.Socket.<init>(Socket.java:213) at com.jcraft.jsch.Util$1.run(Util.java:362) Caused: com.jcraft.jsch.JSchException at com.jcraft.jsch.Util.createSocket(Util.java:394) at com.jcraft.jsch.Session.connect(Session.java:215) at com.jcraft.jsch.Session.connect(Session.java:183) at com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher.getRemoteSession(AzureVMAgentSSHLauncher.java:307) at com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher.connectToSsh(AzureVMAgentSSHLauncher.java:453) at com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher.launch(AzureVMAgentSSHLauncher.java:115) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834)
Every jobs are now failing because of ssh connection issues, we didn't change anything in our configuration, and it doesn't seem to have any network issues
Jie Shen The issue seems more global than a network issue, as you can see on this public jenkins instance 'ci.jenkins.io' no vm are created anymore with the azure-vm-agent plugin. Would it be possible to be caused by an outdated api on azure side?
Olivier Vernin it is possible to be caused by some outdated arm template. I want to confirm if the agents have been created successfully and in healthy state. If not, could you please provide any provisioning log to indicate which prevents to provision the new agents.