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

Agent is not connected after updating to 2.425 version

      After updating to Jenkins all builds stuck with the following records in logs. According to the changelog, I assume that the problem could be related to the following change - The minimum required Remoting version has been increased to 4.13.

       

      [ecs-jenkins-sonar-scanner-dotnet-50fjd]: Waiting for agent to connect Sep 27, 2023 11:08:14 AM WARNING com.cloudbees.jenkins.plugins.amazonecs.ECSLauncher launch [ecs-jenkins-sonar-scanner-dotnet-50fjd]: Error in provisioning; agent=com.cloudbees.jenkins.plugins.amazonecs.ECSSlave[ecs-jenkins-sonar-scanner-dotnet-50fjd] Also:   java.lang.Throwable: launched here     at hudson.slaves.SlaveComputer._connect(SlaveComputer.java:286)     at hudson.model.Computer.connect(Computer.java:448)     at hudson.slaves.CloudRetentionStrategy.start(CloudRetentionStrategy.java:75)     at org.jenkinsci.plugins.durabletask.executors.OnceRetentionStrategy.start(OnceRetentionStrategy.java:83)     at org.jenkinsci.plugins.durabletask.executors.OnceRetentionStrategy.start(OnceRetentionStrategy.java:46)     at hudson.model.AbstractCIBase.createNewComputerForNode(AbstractCIBase.java:192)     at hudson.model.AbstractCIBase.updateNewComputer(AbstractCIBase.java:221)     at jenkins.model.Jenkins.updateNewComputer(Jenkins.java:1701)     at jenkins.model.Nodes.addNode(Nodes.java:144)     at jenkins.model.Jenkins.addNode(Jenkins.java:2259)     at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:248)     at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:823)     at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:92)     at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:67)     at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)     at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)     at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)     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:829) java.lang.IllegalStateException: Agent is not connected     at com.cloudbees.jenkins.plugins.amazonecs.ECSLauncher.waitForAgent(ECSLauncher.java:204)     at com.cloudbees.jenkins.plugins.amazonecs.ECSLauncher.launch(ECSLauncher.java:113)     at hudson.slaves.SlaveComputer.lambda$_connect$0(SlaveComputer.java:297)     at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)     at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:80)     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:829)

          [JENKINS-72096] Agent is not connected after updating to 2.425 version

          Mark Waite added a comment -

          If the issue is that the remoting version on the agent containers is older than 4.13, then you'll need to update your Jenkins configuration to use newer agent containers.

          If you're using the example described at https://github.com/aws-samples/jenkins-on-aws/blob/4eb20872954c83b9b5cfc9d1853f9815ecc3000c/cdk/docker/worker/Dockerfile then you'll need to create a new container agent image that uses the image name `jenkins/inbound-agent` instead of using the deprecated `jenkins/jnlp-slave`.

          Mark Waite added a comment - If the issue is that the remoting version on the agent containers is older than 4.13, then you'll need to update your Jenkins configuration to use newer agent containers. If you're using the example described at https://github.com/aws-samples/jenkins-on-aws/blob/4eb20872954c83b9b5cfc9d1853f9815ecc3000c/cdk/docker/worker/Dockerfile then you'll need to create a new container agent image that uses the image name `jenkins/inbound-agent` instead of using the deprecated `jenkins/jnlp-slave`.

            roehrijn2 Jan Roehrich
            support_s support
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: