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

durable-task v1.33 fails with agent Dockerfile

    Details

    • Similar Issues:

      Description

      Error I get
      process apparently never started in /home/ec2-user/workspace/ntend-pipeline_customer-settings@3@tmp/durable-f026a6cb
      (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)
      Cannot contact EC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5): java.io.FileNotFoundException: File '/home/ec2-user/workspace/ntend-pipeline_customer-settings@3@tmp/durable-f026a6cb/output.txt' does not existHard kill!

      Stack trace:

      Nov 26, 2019 3:17:48 PM FINER org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
      EC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) seems to be online so using /home/ec2-user/workspace/ntend-pipeline_customer-settings@3 
      Nov 26, 2019 3:17:48 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
      could not check /home/ec2-user/workspace/ntend-pipeline_customer-settings@3 
          Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to EC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5)
              at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743)
              at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
              at hudson.remoting.Channel.call(Channel.java:957)
              at hudson.FilePath.act(FilePath.java:1072)
              at hudson.FilePath.act(FilePath.java:1061)
              at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.getOutput(FileMonitoringTask.java:300)
              at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.getOutput(FileMonitoringTask.java:293)
              at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.lambda$check$3(DurableTaskStep.java:604)
              at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.handleExit(DurableTaskStep.java:651)
              at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:604)
              at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:548)
              at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
              at java.util.concurrent.FutureTask.run(FutureTask.java:266)
              at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
              at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
      java.io.FileNotFoundException: File '/home/ec2-user/workspace/ntend-pipeline_customer-settings@3@tmp/durable-a112d9e1/output.txt' does not exist
          at org.apache.commons.io.FileUtils.openInputStream(FileUtils.java:297)
          at org.apache.commons.io.FileUtils.readFileToByteArray(FileUtils.java:1851)
          at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1.invoke(FileMonitoringTask.java:302)
          at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1.invoke(FileMonitoringTask.java:300)
          at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3052)
          at hudson.remoting.UserRequest.perform(UserRequest.java:212)
          at hudson.remoting.UserRequest.perform(UserRequest.java:54)
          at hudson.remoting.Request$2.run(Request.java:369)
          at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
          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:748)
      
      

        Attachments

          Activity

          Hide
          dnusbaum Devin Nusbaum added a comment -

          Marky Jackson You mean formatting is not working in Jira? I think if you just use the non-WYSIWYG editor and surround whatever your text is in {noformat} it will work fine. It looks like your build log still contains:

          [Pipeline] sh process apparently never started in /home/${USER}/workspace/ntend-pipeline_customer-settings@tmp/durable-d4083a8e (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)
          

          Which I think still means that the LAUNCH_DIAGNOSTICS is still false. Did you restart Jenkins after setting the property? If you don't want to restart Jenkins, I think you can run "org.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true" from the script console to enable it temporarily (not sure if Groovy will let you change the field though since it is private).

          Show
          dnusbaum Devin Nusbaum added a comment - Marky Jackson You mean formatting is not working in Jira? I think if you just use the non-WYSIWYG editor and surround whatever your text is in {noformat} it will work fine. It looks like your build log still contains: [Pipeline] sh process apparently never started in /home/${USER}/workspace/ntend-pipeline_customer-settings@tmp/durable-d4083a8e (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer) Which I think still means that the LAUNCH_DIAGNOSTICS is still false. Did you restart Jenkins after setting the property? If you don't want to restart Jenkins, I think you can run "org.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true" from the script console to enable it temporarily (not sure if Groovy will let you change the field though since it is private).
          Hide
          jequals5 Marky Jackson added a comment -

          I did a restart Devin Nusbaum. I did also just try running it in the script console

          Show
          jequals5 Marky Jackson added a comment - I did a restart Devin Nusbaum . I did also just try running it in the script console
          Hide
          dnusbaum Devin Nusbaum added a comment - - edited

          Marky Jackson Once you got LAUNCH_DIAGNOSTICS enabled, did the build log have any additional information? If not, can you downgrade to Durable Task Plugin 1.30 (and Pipeline: Nodes and Processes 2.34) to see if things work correctly in that version? CC Carroll Chiou, potentially related to JENKINS-60107, or maybe JENKINS-60054 unless that is Kubernetes-specific?

          Show
          dnusbaum Devin Nusbaum added a comment - - edited Marky Jackson Once you got LAUNCH_DIAGNOSTICS enabled, did the build log have any additional information? If not, can you downgrade to Durable Task Plugin 1.30 (and Pipeline: Nodes and Processes 2.34) to see if things work correctly in that version? CC Carroll Chiou , potentially related to  JENKINS-60107 , or maybe JENKINS-60054 unless that is Kubernetes-specific?
          Hide
          jequals5 Marky Jackson added a comment -

          Devin Nusbaum at this point it appears someone upgraded a plugin which in turn upgraded 1.29 to 1.33 and that broke all the dependancies.

          I moved everything back to native docker calls as Jesse Glick alluded to

           

          Show
          jequals5 Marky Jackson added a comment - Devin Nusbaum at this point it appears someone upgraded a plugin which in turn upgraded 1.29 to 1.33 and that broke all the dependancies. I moved everything back to native docker calls as Jesse Glick alluded to  
          Hide
          dnusbaum Devin Nusbaum added a comment -

          Marky Jackson Ok, if you end up with any additional information from LAUNCH_DIAGNOSTICS, or if you can figure out whether 1.30 has the same problem, feel free to add the info here. I am going to close the ticket.

          Show
          dnusbaum Devin Nusbaum added a comment - Marky Jackson Ok, if you end up with any additional information from LAUNCH_DIAGNOSTICS, or if you can figure out whether 1.30 has the same problem, feel free to add the info here. I am going to close the ticket.

            People

            • Assignee:
              Unassigned
              Reporter:
              jequals5 Marky Jackson
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: