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

Agent fails to download Amazon S3 artifacts using pipeline-aws-plugin

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Blocker Blocker
    • core
    • None
    • Jenkins 2.261

      Jenkins slave connected via an ssh hangs on downloading Amazon S3 artifacts using s3Download feature of pipeline-aws-plugin (Pipeline: AWS Steps). As a result build finishes as aborted as the timeout specified for pipeline stage is reached:

       Timeout has been exceeded
       java.lang.InterruptedException
       at java.lang.Object.wait(Native Method)
       at hudson.remoting.Request.call(Request.java:176)
       at hudson.remoting.Channel.call(Channel.java:1000)
       at hudson.FilePath.act(FilePath.java:1070)
       at hudson.FilePath.act(FilePath.java:1059)
       at de.taimos.pipeline.aws.S3DownloadStep$Execution.run(S3DownloadStep.java:149)
       at de.taimos.pipeline.aws.S3DownloadStep$Execution.run(S3DownloadStep.java:113)
       at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
       at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
       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)
       Finished: ABORTED
      
      

      Master node is not affected.

      NOTE: Rolling back to 2.260 version corrects the problem. 
       
       

          [JENKINS-63947] Agent fails to download Amazon S3 artifacts using pipeline-aws-plugin

          Gleb Tereshkov created issue -
          Gleb Tereshkov made changes -
          Description Original: Jenkins slave connected via an ssh hangs on downloading Amazon S3 artifacts using [s3Download|https://github.com/jenkinsci/pipeline-aws-plugin#s3download] feature of pipeline-aws-plugin. As a result build finishes as aborted as the timeout specified for pipeline stage is reached:
          Timeout has been exceeded
          java.lang.InterruptedException
          at java.lang.Object.wait(Native Method)
          at hudson.remoting.Request.call(Request.java:176)
          at hudson.remoting.Channel.call(Channel.java:1000)
          at hudson.FilePath.act(FilePath.java:1070)
          at hudson.FilePath.act(FilePath.java:1059)
          at de.taimos.pipeline.aws.S3DownloadStep$Execution.run(S3DownloadStep.java:149)
          at de.taimos.pipeline.aws.S3DownloadStep$Execution.run(S3DownloadStep.java:113)
          at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
          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)
          Finished: ABORTED
          Master node is not affected.

          *NOTE*: Rolling back to 2.260 version corrects the problem. 
           
           
          New: Jenkins slave connected via an ssh hangs on downloading Amazon S3 artifacts using [s3Download|https://github.com/jenkinsci/pipeline-aws-plugin#s3download] feature of pipeline-aws-plugin. As a result build finishes as aborted as the timeout specified for pipeline stage is reached:

          {noformat}
           Timeout has been exceeded
           java.lang.InterruptedException
           at java.lang.Object.wait(Native Method)
           at hudson.remoting.Request.call(Request.java:176)
           at hudson.remoting.Channel.call(Channel.java:1000)
           at hudson.FilePath.act(FilePath.java:1070)
           at hudson.FilePath.act(FilePath.java:1059)
           at de.taimos.pipeline.aws.S3DownloadStep$Execution.run(S3DownloadStep.java:149)
           at de.taimos.pipeline.aws.S3DownloadStep$Execution.run(S3DownloadStep.java:113)
           at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
           at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
           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)
           Finished: ABORTED

          {noformat}


           Master node is not affected.

          *NOTE*: Rolling back to 2.260 version corrects the problem. 
            
            
          Gleb Tereshkov made changes -
          Description Original: Jenkins slave connected via an ssh hangs on downloading Amazon S3 artifacts using [s3Download|https://github.com/jenkinsci/pipeline-aws-plugin#s3download] feature of pipeline-aws-plugin. As a result build finishes as aborted as the timeout specified for pipeline stage is reached:

          {noformat}
           Timeout has been exceeded
           java.lang.InterruptedException
           at java.lang.Object.wait(Native Method)
           at hudson.remoting.Request.call(Request.java:176)
           at hudson.remoting.Channel.call(Channel.java:1000)
           at hudson.FilePath.act(FilePath.java:1070)
           at hudson.FilePath.act(FilePath.java:1059)
           at de.taimos.pipeline.aws.S3DownloadStep$Execution.run(S3DownloadStep.java:149)
           at de.taimos.pipeline.aws.S3DownloadStep$Execution.run(S3DownloadStep.java:113)
           at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
           at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
           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)
           Finished: ABORTED

          {noformat}


           Master node is not affected.

          *NOTE*: Rolling back to 2.260 version corrects the problem. 
            
            
          New: Jenkins slave connected via an ssh hangs on downloading Amazon S3 artifacts using [s3Download|https://github.com/jenkinsci/pipeline-aws-plugin#s3download] feature of pipeline-aws-plugin ([Pipeline: AWS Steps|https://plugins.jenkins.io/pipeline-aws/]). As a result build finishes as aborted as the timeout specified for pipeline stage is reached:
          {noformat}
           Timeout has been exceeded
           java.lang.InterruptedException
           at java.lang.Object.wait(Native Method)
           at hudson.remoting.Request.call(Request.java:176)
           at hudson.remoting.Channel.call(Channel.java:1000)
           at hudson.FilePath.act(FilePath.java:1070)
           at hudson.FilePath.act(FilePath.java:1059)
           at de.taimos.pipeline.aws.S3DownloadStep$Execution.run(S3DownloadStep.java:149)
           at de.taimos.pipeline.aws.S3DownloadStep$Execution.run(S3DownloadStep.java:113)
           at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
           at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
           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)
           Finished: ABORTED

          {noformat}
          Master node is not affected.

          *NOTE*: Rolling back to 2.260 version corrects the problem. 
            
            

          Oleg Nenashev added a comment -

          Taking the stacktrace, it is almost certainly another symptom of JENKINS-63933

          Oleg Nenashev added a comment - Taking the stacktrace, it is almost certainly another symptom of JENKINS-63933
          Oleg Nenashev made changes -
          Link New: This issue duplicates JENKINS-63933 [ JENKINS-63933 ]
          Oleg Nenashev made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Unassigned Unassigned
            glebtereshkov Gleb Tereshkov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: