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

Failed to extract workspace.tar.gz when cloning workspace

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • Jenkins version 1.580.1
      Clone Workspace SCM Plugin .6
      Jenkins OS is Linux 2.6.18-308.11.1.el5

      We are seeing intermittent errors on jobs using the Clone Workspace SCM Plugin. Job A kicks off dependent/downstream builds Job B, C, and D, and many times one of the dependent builds will fail with the following stack trace:

      Started by upstream project "synthetics-01-build_test_findbugs" build number 853
      originally caused by:
      Started by remote host GitHub via SQS with note: SQS poll initiated on Nov 5, 2014 12:23:01 PM
      [EnvInject] - Loading node environment variables.
      Building remotely on synthetics-test-01 (synthetics-build) in workspace /home/jenkins/workspace/synthetics-02-docker-build-scheduler
      Restoring workspace from build #853 of project synthetics-01-build_test_findbugs
      java.io.IOException: remote file operation failed: /home/jenkins/workspace/synthetics-02-docker-build-scheduler at hudson.remoting.Channel@17aba278:synthetics-test-01: java.io.IOException: Failed to extract workspace.tar.gz
      at hudson.FilePath.act(FilePath.java:976)
      at hudson.FilePath.act(FilePath.java:958)
      at hudson.FilePath.untar(FilePath.java:518)
      at hudson.plugins.cloneworkspace.CloneWorkspacePublisher$WorkspaceSnapshotTar.restoreTo(CloneWorkspacePublisher.java:243)
      at hudson.plugins.cloneworkspace.CloneWorkspaceSCM$Snapshot.restoreTo(CloneWorkspaceSCM.java:396)
      at hudson.plugins.cloneworkspace.CloneWorkspaceSCM.checkout(CloneWorkspaceSCM.java:152)
      at hudson.model.AbstractProject.checkout(AbstractProject.java:1253)
      at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
      at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
      at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)
      at hudson.model.Run.execute(Run.java:1745)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      at hudson.model.ResourceController.execute(ResourceController.java:89)
      at hudson.model.Executor.run(Executor.java:240)
      Caused by: java.io.IOException: Failed to extract workspace.tar.gz
      at hudson.FilePath.readFromTar(FilePath.java:2198)
      at hudson.FilePath.access$400(FilePath.java:190)
      at hudson.FilePath$4.invoke(FilePath.java:520)
      at hudson.FilePath$4.invoke(FilePath.java:518)
      at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2577)
      at hudson.remoting.UserRequest.perform(UserRequest.java:121)
      at hudson.remoting.UserRequest.perform(UserRequest.java:49)
      at hudson.remoting.Request$2.run(Request.java:324)
      at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
      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:745)
      at ......remote call to synthetics-test-01(Native Method)
      at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
      at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
      at hudson.remoting.Channel.call(Channel.java:752)
      at hudson.FilePath.act(FilePath.java:969)
      ... 13 more
      Caused by: java.io.IOException: incorrect header check
      at com.jcraft.jzlib.InflaterInputStream.read(InflaterInputStream.java:112)
      at org.apache.tools.tar.TarBuffer.readBlock(TarBuffer.java:257)
      at org.apache.tools.tar.TarBuffer.readRecord(TarBuffer.java:223)
      at hudson.org.apache.tools.tar.TarInputStream.getNextEntry(TarInputStream.java:228)
      at hudson.FilePath.readFromTar(FilePath.java:2175)
      at hudson.FilePath.access$400(FilePath.java:190)
      at hudson.FilePath$4.invoke(FilePath.java:520)
      at hudson.FilePath$4.invoke(FilePath.java:518)
      at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2577)
      at hudson.remoting.UserRequest.perform(UserRequest.java:121)
      at hudson.remoting.UserRequest.perform(UserRequest.java:49)
      at hudson.remoting.Request$2.run(Request.java:324)
      at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
      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:745)
      Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
      Notifying upstream projects of job completion
      Finished: FAILURE

      Things we checked:

      • Build #853 had a workspace at the time of this build.
      • Build #853 (the parent build, aka Job A) is configured not to begin a new build until all downstream builds have finished, so there shouldn't be any sort of workspace switching going on.

          [JENKINS-25462] Failed to extract workspace.tar.gz when cloning workspace

          I've also been seeing the same issue sporadically in my jobs. It's a similar structure:

          We have one multi-job in which the first job does a checkout and archive of the workspace 9using the clone plugin). In the subsequent phases, we unarchive the workspace and build. However, the downstream jobs in those phases occasionally hit this exception.

          Deepu Sudhakar added a comment - I've also been seeing the same issue sporadically in my jobs. It's a similar structure: We have one multi-job in which the first job does a checkout and archive of the workspace 9using the clone plugin). In the subsequent phases, we unarchive the workspace and build. However, the downstream jobs in those phases occasionally hit this exception.

          I have same issue in similar condition. Is there any workarounds for this issue?

          Rezo Heorhadze added a comment - I have same issue in similar condition. Is there any workarounds for this issue?

          Yep, I see the same issue. So frustrating as is it so intermittent!

          Guillaume Egles added a comment - Yep, I see the same issue. So frustrating as is it so intermittent!

            Unassigned Unassigned
            alicegoldfuss Alice Goldfuss
            Votes:
            4 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: