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

Remote.jar is not working anymore because of changed parameter slave.jar->agent.jar

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • docker-plugin

    Description

      I use the docker plugin to execute jobs remote in another docker-container. I configured the cloud with default parameters and the "connect method": "Attach Docker container". When i execute a job, i get the message, that the used parameter "-slaveLog" is invalid. 

      The reason for that is, that Jeff removed the parameter alias in version 4.6 of remoting.jar so just "-agentLog" is valid now (pull request here). With jenkins 2.266 the remote-4.6.jar is the new default, so the docker-plugin's default settings (for the "Attach" method) are no longer viable - it's now necessary to override the defaults to make it work.

      Attachments

        Activity

          frickeldave David Koenig created issue -
          frickeldave David Koenig made changes -
          Field Original Value New Value
          Link This issue duplicates INFRA-2817 [ INFRA-2817 ]
          frickeldave David Koenig made changes -
          Summary Remote.jar is not working anymore becuase of changed parameter slave.jar->agent.jar Remote.jar is not working anymore because of changed parameter slave.jar->agent.jar
          frickeldave David Koenig made changes -
          Environment Jenkins 266 (not solved 267)
          Docker plugin 1.2.1
          OS Debian 9
          Jenkins in Docker container (Based on Debian)
          Jenkins-Slave Docker Image (Based on Debian)
          Java 11 is used in master and slave container
          Jenkins 266 (not solved in 267)
          Docker plugin 1.2.1
          OS Debian 9
          Jenkins in Docker container (Based on Debian)
          Jenkins-Slave Docker Image (Based on Debian)
          Java 11 is used in master and slave container
          frickeldave David Koenig made changes -
          Environment Jenkins 266 (not solved in 267)
          Docker plugin 1.2.1
          OS Debian 9
          Jenkins in Docker container (Based on Debian)
          Jenkins-Slave Docker Image (Based on Debian)
          Java 11 is used in master and slave container
          Jenkins 266 (not solved in 267)
          Docker plugin 1.2.1
          OS Debian 9
          Docker version 19.03.13
          Jenkins in Docker container (Based on Debian)
          Jenkins-Slave Docker Image (Based on Debian)
          Java 11 is used in master and slave container
          frickeldave David Koenig made changes -
          Comment [ I accidentaly created the issue INFRA-2817 before, but i am not able to delete that.  ]
          pjdarton pjdarton made changes -
          Environment Jenkins 266 (not solved in 267)
          Docker plugin 1.2.1
          OS Debian 9
          Docker version 19.03.13
          Jenkins in Docker container (Based on Debian)
          Jenkins-Slave Docker Image (Based on Debian)
          Java 11 is used in master and slave container
          Jenkins 2.266 (not solved in 267)
          Docker plugin 1.2.1
          OS Debian 9
          Docker version 19.03.13
          Jenkins in Docker container (Based on Debian)
          Jenkins-Slave Docker Image (Based on Debian)
          Java 11 is used in master and slave container
          pjdarton pjdarton made changes -
          Description I use the docker plugin to execute jobs remote in another docker-container. I configured the cloud with default parameters and the "connect method": "Attach Docker container". When i execute a job, i get the message, that the used parameter "-slaveLog" is invalid. 

          The reason for that is, that Jeff removed t[he parameter alias|https://groups.google.com/g/jenkinsci-users/c/ZWdWjYbfmPI] in version 4.6 of remoting.jar so just "-agentLog" is valid now (pull request [here|https://github.com/jenkinsci/remoting/pull/416]). With jenkins 2.266 the remote-4.6.jar is the new default, so no builds are possible now with docker plugin. 

           

           
          I use the docker plugin to execute jobs remote in another docker-container. I configured the cloud with default parameters and the "connect method": "Attach Docker container". When i execute a job, i get the message, that the used parameter "-slaveLog" is invalid. 

          The reason for that is, that Jeff removed t[he parameter alias|https://groups.google.com/g/jenkinsci-users/c/ZWdWjYbfmPI] in version 4.6 of remoting.jar so just "-agentLog" is valid now (pull request [here|https://github.com/jenkinsci/remoting/pull/416]). With jenkins 2.266 the remote-4.6.jar is the new default, so the docker-plugin's default settings (for the "Attach" method) are no longer viable - it's now necessary to override the defaults to make it work.
          pjdarton pjdarton made changes -
          Assignee Nicolas De Loof [ ndeloof ] pjdarton [ pjdarton ]
          pjdarton pjdarton made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          pjdarton pjdarton made changes -
          Resolution Fixed [ 1 ]
          Status In Progress [ 3 ] Fixed but Unreleased [ 10203 ]
          frickeldave David Koenig made changes -
          Comment [ Hi, 

          sorry for the delay, had some other topics to solve. But now i tested it. I installed the referenced version. Now i didn't get any error message but nothing happens. The output of jenkins says: 
          {quote} 
          {code:java}
          ...
          ...
          2021-01-25 22:04:57.418+0000 [id=872] INFO c.n.j.p.docker.DockerTemplate#doProvisionNode: Trying to run container for image ".../cid-jenkins-debian-slave:latest"
          2021-01-25 22:04:57.419+0000 [id=872] INFO c.n.j.p.docker.DockerTemplate#doProvisionNode: Trying to run container for node lcl_cid-jenkins-debian-slave-0002qa5i1lju8 from image: .../cid-jenkins-debian-slave:latest
          2021-01-25 22:04:57.471+0000 [id=872] INFO c.n.j.p.docker.DockerTemplate#doProvisionNode: Started container ID 999bf690189d002e788164d392994eaa2aa051676ae60f684e69f81db88fa34f for node lcl_cid-jenkins-debian-slave-0002qa5i1lju8 from image: .../cid-jenkins-debian-slave:latest
          2021-01-25 22:05:07.393+0000 [id=36] INFO hudson.slaves.NodeProvisioner#lambda$update$6: Image of .../cid-jenkins-debian-slave:latest provisioning successfully completed. We have now 6 computer(s)
          2021-01-25 22:05:07.401+0000 [id=36] INFO c.n.j.plugins.docker.DockerCloud#canAddProvisionedAgent: Provisioning '.../cid-jenkins-debian-slave:latest' on 'lcl-slave-cloud'; Total containers: 5 (of 6)
          2021-01-25 22:05:07.402+0000 [id=36] INFO c.n.j.plugins.docker.DockerCloud#provision: Will provision '.../cid-jenkins-debian-slave:latest', for label: 'lcl_cid-jenkins-debian-slave', in cloud: 'lcl-slave-cloud'
          2021-01-25 22:05:07.406+0000 [id=869] INFO c.n.j.p.docker.DockerTemplate#doProvisionNode: Trying to run container for image "...s/cid-jenkins-debian-slave:latest"
          2021-01-25 22:05:07.407+0000 [id=869] INFO c.n.j.p.docker.DockerTemplate#doProvisionNode: Trying to run container for node lcl_cid-jenkins-debian-slave-0002qaa38dv98 from image: .../cid-jenkins-debian-slave:latest
          2021-01-25 22:05:07.407+0000 [id=36] INFO h.s.NodeProvisioner$StandardStrategyImpl#apply: Started provisioning Image of ..../cid-jenkins-debian-slave:latest from lcl-slave-cloud with 1 executors. Remaining excess workload: 0
          2021-01-25 22:05:07.470+0000 [id=869] INFO c.n.j.p.docker.DockerTemplate#doProvisionNode: Started container ID 7887c8933316fce8a5b1064813696e6424e69b1049a24d97b06b96258125bad9 for node lcl_cid-jenkins-debian-slave-0002qaa38dv98 from image: .../cid-jenkins-debian-slave:latest
          2021-01-25 22:05:17.393+0000 [id=35] INFO hudson.slaves.NodeProvisioner#lambda$update$6: Image of .../cid-jenkins-debian-slave:latest provisioning successfully completed. We have now 7 computer(s)
          2021-01-25 22:05:55.757+0000 [id=891] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$0: Started DockerContainerWatchdog Asynchronous Periodic Work
          2021-01-25 22:05:55.758+0000 [id=891] INFO c.n.j.p.d.DockerContainerWatchdog#execute: Docker Container Watchdog has been triggered
          2021-01-25 22:05:55.758+0000 [id=891] INFO c.n.j.p.d.DockerContainerWatchdog$Statistics#writeStatisticsToLog: Watchdog Statistics: Number of overall executions: 17, Executions with processing timeout: 0, Containers removed gracefully: 5, Containers removed with force: 0, Containers removal failed: 0, Nodes removed successfully: 7, Nodes removal failed: 0, Container removal average duration (gracefully): 1712 ms, Container removal average duration (force): 0 ms, Average overall runtime of watchdog: 754 ms, Average runtime of container retrieval: 120 ms
          2021-01-25 22:05:55.759+0000 [id=891] INFO c.n.j.p.d.DockerContainerWatchdog#loadNodeMap: We currently have 6 nodes assigned to this Jenkins instance, which we will check
          2021-01-25 22:05:55.760+0000 [id=891] INFO c.n.j.p.d.DockerContainerWatchdog#execute: Checking Docker Cloud lcl-slave-cloud at unix:///var/run/docker.sock
          2021-01-25 22:05:55.788+0000 [id=891] INFO c.n.j.p.d.DockerContainerWatchdog#execute: Docker Container Watchdog check has been completed
          2021-01-25 22:05:55.791+0000 [id=891] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$0: Finished DockerContainerWatchdog Asynchronous Periodic Work. 30 ms
          {code}
           
          {quote}
           

          So the container start and it seems successful, but the console just shows me, that the node is offline.  

          The Thread dump (http://JENKINS_SERVER/job/.../.../threadDump) shows me the following content: 


          at DSL.node(waiting for part of master » 20 - Integrationtest #8 to be scheduled; blocked: All nodes of label ‘lcl_cid-jenkins-debian-slave’ are offline)
          at org.jenkinsci.plugins.pipeline.modeldefinition.agent.impl.LabelScript.run(LabelScript.groovy:42)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.inDeclarativeAgent(ModelInterpreter.groovy:589)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage(ModelInterpreter.groovy:272)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.stageInput(ModelInterpreter.groovy:356)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.stageInput(ModelInterpreter.groovy:355)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage(ModelInterpreter.groovy:261)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.inWrappers(ModelInterpreter.groovy:613)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.inWrappers(ModelInterpreter.groovy:612)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage(ModelInterpreter.groovy:259)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.withEnvBlock(ModelInterpreter.groovy:443)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.withEnvBlock(ModelInterpreter.groovy:442)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage(ModelInterpreter.groovy:254)
          at DSL.stage(Native Method)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage(ModelInterpreter.groovy:240)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateSequentialStages(ModelInterpreter.groovy:172)
          at com.cloudbees.groovy.cps.CpsDefaultGroovyMethods.each(CpsDefaultGroovyMethods:2030)
          at com.cloudbees.groovy.cps.CpsDefaultGroovyMethods.each(CpsDefaultGroovyMethods:2015)
          at com.cloudbees.groovy.cps.CpsDefaultGroovyMethods.each(CpsDefaultGroovyMethods:2056)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateSequentialStages(ModelInterpreter.groovy:157)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.call(ModelInterpreter.groovy:84)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.toolsBlock(ModelInterpreter.groovy:544)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.toolsBlock(ModelInterpreter.groovy:543)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.call(ModelInterpreter.groovy:83)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.recursiveWrappers(ModelInterpreter.groovy:628)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.recursiveWrappers(ModelInterpreter.groovy:627)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.inWrappers(ModelInterpreter.groovy:609)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.inWrappers(ModelInterpreter.groovy:608)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.call(ModelInterpreter.groovy:79)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.withEnvBlock(ModelInterpreter.groovy:443)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.withEnvBlock(ModelInterpreter.groovy:442)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.call(ModelInterpreter.groovy:78)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.withCredentialsBlock(ModelInterpreter.groovy:481)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.withCredentialsBlock(ModelInterpreter.groovy:480)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.call(ModelInterpreter.groovy:77)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.inDeclarativeAgent(ModelInterpreter.groovy:590)
          at org.jenkinsci.plugins.pipeline.modeldefinition.agent.CheckoutScript.checkoutAndRun(CheckoutScript.groovy:64)
          at org.jenkinsci.plugins.pipeline.modeldefinition.agent.CheckoutScript.doCheckout(CheckoutScript.groovy:40)
          at org.jenkinsci.plugins.pipeline.modeldefinition.agent.impl.LabelScript.run(LabelScript.groovy:43)
          at DSL.node(running on )
          at org.jenkinsci.plugins.pipeline.modeldefinition.agent.impl.LabelScript.run(LabelScript.groovy:42)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.inDeclarativeAgent(ModelInterpreter.groovy:589)
          at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.call(ModelInterpreter.groovy:76)
          at WorkflowScript.run(WorkflowScript:2)
           

          Any idea for me, what to try next? 

          Regards


          Dave ]
          pjdarton pjdarton made changes -
          Status Fixed but Unreleased [ 10203 ] Resolved [ 5 ]

          People

            pjdarton pjdarton
            frickeldave David Koenig
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: