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

Docker builds fail with "Build info capturing failed for docker image..." exception

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • artifactory-plugin
    • RHEL 7.2, Docker version 1.12.3, Jenkins 2.19.1(running in Docker, no agents, only master), Artifactory 4.14.1, Artifactory Plugin 2.8.1

      Description: I followed Jenkins Artifactory Plugin - Setting Up Docker Build Info and got

      java.lang.IllegalStateException: Build info capturing failed for docker image: artifactory.mycompany.com/mycompany/myproject/myservice:0.0.1.c62f0c8.72 check build info proxy configuration.
        at org.jfrog.hudson.pipeline.steps.DockerPushStep$Execution.run(DockerPushStep.java:104)
        at org.jfrog.hudson.pipeline.steps.DockerPushStep$Execution.run(DockerPushStep.java:61)
        at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousStepExecution.start(AbstractSynchronousStepExecution.java:40)
        ...
      

      Docker/Server Setup:

      • Instead of using only HTTP_PROXY in /etc/systemd/system/docker.service.d/http-proxy.conf, I also added NO_PROXY to be able to access to Artifactory artifactory.mycompany.com. Please note that adding or removing HTTPS_PROXY does not change anyting. None of the following configurations worked:
        /etc/systemd/system/docker.service.d/http-proxy.conf
        Environment="HTTP_PROXY=http://localhost:9765" "NO_PROXY=.mycompany.com"
        #Environment="HTTP_PROXY=http://localhost:9765" "HTTPS_PROXY=http://localhost:9765" "NO_PROXY=.mycompany.com"
        #Environment="HTTP_PROXY=http://10.74.200.52:9765" "NO_PROXY=localhost,127.0.0.0/8,.mycompany.com"
        #Environment="HTTP_PROXY=http://10.74.200.52:9765" "HTTPS_PROXY=http://10.74.200.52:9765" "NO_PROXY=localhost,127.0.0.0/8,.mycompany.com"
        
      • Although Jenkins Artifactory Plugin - Setting Up Docker Build Info does not mention, I needed to execute sudo chmod 777 /var/run/docker.sock command to prevent following error:
        javax.ws.rs.ProcessingException: org.newsclub.net.unix.AFUNIXSocketException: Permission denied (socket: /run/docker.sock)
          at com.github.dockerjava.jaxrs.connector.ApacheConnector.apply(ApacheConnector.java:484)
          at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:246)
          at org.glassfish.jersey.client.JerseyInvocation$2.call(JerseyInvocation.java:683)
          ...
          at com.github.dockerjava.core.command.InspectImageCmdImpl.exec(InspectImageCmdImpl.java:40)
          at org.jfrog.hudson.pipeline.docker.utils.DockerUtils.getImageIdFromTag(DockerUtils.java:33)
          at org.jfrog.hudson.pipeline.docker.utils.DockerAgentUtils$2.call(DockerAgentUtils.java:67)
          at org.jfrog.hudson.pipeline.docker.utils.DockerAgentUtils$2.call(DockerAgentUtils.java:65)
          at hudson.remoting.LocalChannel.call(LocalChannel.java:45)
          at org.jfrog.hudson.pipeline.docker.utils.DockerAgentUtils.registerImage(DockerAgentUtils.java:65)
        

      Jenkins Setup:

      • There is no Jenkins agent and Jenkins master runs in Docker container.
      • To be able to run docker command in the container, I prefered Docker outside of Docker(dood) solution
      • exposed port 9765 for Artifactory Plugin's internal proxy
      • used volume for Jenkins's data
      • ran Jenkins container as swarm service
      • Followed Jenkins Artifactory Plugin - Setting Up Docker Build Info by choosing port 9765
      Dockerfile.myjenkins
      FROM artifactory.mycompany.com/jenkins
      
      USER root
      
      # To be able to build Docker images within the container, we have chosen 
      # Docker outside of Docker(dood) solution in preference to Docker in 
      # Docker(dind). By using dood we are able to execute "docker" commands
      # without installing Docker into the container. See following
      # pages to get better understanding of all the benefits of dood:
      # - Jenkins with DooD (Docker outside of Docker): https://github.com/axltxl/docker-jenkins-dood
      # - Running Docker in Jenkins (in Docker): http://container-solutions.com/running-docker-in-jenkins-in-docker/
      RUN apt-get update \
       && apt-get install -y sudo \
       && rm -rf /var/lib/apt/lists/* \
       && echo "jenkins ALL=NOPASSWD: ALL" >> /etc/sudoers \
       && printf '#!/bin/bash\nsudo docker.bin "$@"\n' > /usr/local/bin/docker \
       && chmod +x /usr/local/bin/docker
      
      USER jenkins
      
      # Artifactory Plug-in's build-in proxy for Docker images: 
      # https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Artifactory+Plugin+-+Setting+Up+Docker+Build+Info#JenkinsArtifactoryPlugin-SettingUpDockerBuildInfo-EnabletheJenkinsBuildInfoProxy
      EXPOSE 9765
      
      Build & Push myjenkins Image
      docker build -f Dockerfile.myjenkins -t artifactory.mycompany.com/myjenkins .
      ...
      docker push artifactory.mycompany.com/myjenkins
      
      Create myjenkins Swarm Service
      docker service create --name myjenkins -p 8080:8080 -p 50000:50000 -p 9765:9765 --replicas 1 \
        --mount type=bind,src=/var/run/docker.sock,dst=/var/run/docker.sock,readonly \
        --mount type=bind,src=$(which docker),dst=/usr/bin/docker.bin \
        --mount type=volume,src=volume_myjenkins,dst=/var/jenkins_home \
        artifactory.mkk.com.tr/myjenkins
      

      Setup Test:

      • On host machine;
        • Connected to port 9765 successfully: telnet localhost 9765
        • Executed following docker command successfully:
          docker pull artifactory.mycompany.com/hello-world
          
      • On Jenkins;
        • Created a dummy job and executed the same docker command successfully.

          [JENKINS-40037] Docker builds fail with "Build info capturing failed for docker image..." exception

          Sébastien,
          Looks like you're experiencing an issue similar to this:
          https://issues.jenkins-ci.org/browse/JENKINS-41059
          The Jenkins Artifactory Plugin is managed here:
          https://github.com/JFrogDev/jenkins-artifactory-plugin

          Eyal Ben Moshe added a comment - Sébastien, Looks like you're experiencing an issue similar to this: https://issues.jenkins-ci.org/browse/JENKINS-41059 The Jenkins Artifactory Plugin is managed here: https://github.com/JFrogDev/jenkins-artifactory-plugin

          On class DockerAgentUtils on method updateImageParentOnAgents

          I can see that Jenkins.getInstance().getNodes() does not return master.
          This is why it can not find buidInfo on master agent.

          this Jenkins.getInstance().getChannel() can have access to master

          sébastien glon added a comment - On class DockerAgentUtils on method updateImageParentOnAgents I can see that Jenkins.getInstance().getNodes() does not return master. This is why it can not find buidInfo on master agent. this Jenkins.getInstance().getChannel() can have access to master

          After adding Log on BuildInfoHttpFiltersSource and JenkinsBuildInfoLog, I can see than proxy received buildInfo Data
          But on rtDocker.push, this info is not retreived

          Jan 23, 2017 9:34:23 AM INFO org.jfrog.hudson.pipeline.docker.proxy.BuildInfoHttpFiltersSource filterRequest
          filterRequest: DefaultHttpRequest(decodeResult: success, version: HTTP/1.1)
          HEAD /v2/vscloud/demoapp/blobs/sha256:2c479166ffa8bfcc71460b960771b47046161ec97f8e6576da70ba202962db59 HTTP/1.1
          Host: <my_artifactory_registry>
          User-Agent: docker/1.12.3 go/go1.6.3 git-commit/6b644ec kernel/3.10.0-327.28.3.el7.x86_64 os/linux arch/amd64 UpstreamClient(Jersey/2.23.1 (Apache HttpClient 4.5.1))
          Authorization: Bearer AKCp2VobB17HMYFqxK9kcLm8jgfEbCAK8QCy7ju8q2cxnM9UvGQHhxzcDCtz2eNicvkdMGrVh
          Connection: close
          Jan 23, 2017 9:34:23 AM INFO org.jfrog.hudson.pipeline.docker.proxy.BuildInfoHttpFiltersSource filterRequest
          filterRequest: DefaultHttpRequest(decodeResult: success, version: HTTP/1.1)
          CONNECT <my_artifactory_registry>:443 HTTP/1.1
          Host: <my_artifactory_registry>:443
          User-Agent: Go-http-client/1.1
          Jan 23, 2017 9:34:23 AM INFO org.jfrog.hudson.pipeline.docker.proxy.BuildInfoHttpFiltersSource filterRequest
          filterRequest: DefaultHttpRequest(decodeResult: success, version: HTTP/1.1)
          PUT /v2/vscloud/demoapp/manifests/dev HTTP/1.1
          Host: <my_artifactory_registry>
          User-Agent: docker/1.12.3 go/go1.6.3 git-commit/6b644ec kernel/3.10.0-327.28.3.el7.x86_64 os/linux arch/amd64 UpstreamClient(Jersey/2.23.1 (Apache HttpClient 4.5.1))
          Content-Length: 738
          Authorization: Bearer AKCp2VobB17HMYFqxK9kcLm8jgfEbCAK8QCy7ju8q2cxnM9UvGQHhxzcDCtz2eNicvkdMGrVh
          Content-Type: application/vnd.docker.distribution.manifest.v2+json
          Accept-Encoding: gzip
          Connection: close
          Jan 23, 2017 9:34:23 AM INFO org.jfrog.hudson.pipeline.docker.proxy.BuildInfoFilterAdapter proxyToServerRequest
          Proxy message received: {
          "schemaVersion": 2,
          "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
          "config":

          { "mediaType": "application/vnd.docker.container.image.v1+json", "size": 1937, "digest": "sha256:2c479166ffa8bfcc71460b960771b47046161ec97f8e6576da70ba202962db59" }

          ,
          "layers": [

          { "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip", "size": 668151, "digest": "sha256:56bec22e355981d8ba0878c6c2f23b21f422f30ab0aba188b54f1ffeff59c190" }

          ,

          { "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip", "size": 1522511, "digest": "sha256:b94183b1beb0988d22083e5e60a94474d25be0d0dae4c57e8cb2e07a043a77be" }

          ]
          }
          Jan 23, 2017 9:34:23 AM INFO org.jfrog.hudson.util.JenkinsBuildInfoLog info
          Docker build-info found on node vscloudJenkins-731fabf61c32-host-192-168-0-54.openstacklocal : false
          Jan 23, 2017 9:34:23 AM INFO org.jfrog.hudson.util.JenkinsBuildInfoLog info
          Docker build-info found on node Jenkins : false
          Jan 23, 2017 9:34:23 AM WARNING org.jenkinsci.plugins.workflow.cps.CpsStepContext completed
          already completed CpsStepContext[34:dockerPushStep]:Ownerdev-heat/demo-app/100:dev-heat/demo-app #100
          java.lang.IllegalStateException: delivered here
          at org.jenkinsci.plugins.workflow.cps.CpsStepContext.completed(CpsStepContext.java:351)
          at org.jenkinsci.plugins.workflow.cps.CpsStepContext.onSuccess(CpsStepContext.java:331)
          at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
          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:1142)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
          at java.lang.Thread.run(Thread.java:745)

          Jan 23, 2017 9:34:23 AM INFO org.jenkinsci.plugins.workflow.cps.CpsStepContext completed
          new success: null
          Jan 23, 2017 9:34:23 AM INFO org.jenkinsci.plugins.workflow.cps.CpsStepContext completed
          previously delivered here
          java.lang.Throwable
          at org.jenkinsci.plugins.workflow.cps.CpsStepContext.completed(CpsStepContext.java:339)
          at org.jenkinsci.plugins.workflow.cps.CpsStepContext.onFailure(CpsStepContext.java:327)
          at org.jfrog.hudson.pipeline.steps.DockerPushStep$Execution.run(DockerPushStep.java:105)
          at org.jfrog.hudson.pipeline.steps.DockerPushStep$Execution.run(DockerPushStep.java:62)
          at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
          at hudson.security.ACL.impersonate(ACL.java:260)
          at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
          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:1142)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
          at java.lang.Thread.run(Thread.java:745)

          Jan 23, 2017 9:34:23 AM INFO org.jenkinsci.plugins.workflow.cps.CpsStepContext completed
          earlier failure
          java.lang.IllegalStateException: Build info capturing failed for docker image: docker-<my_artifactory_registry>/vscloud/demoapp:dev check build info proxy configuration.
          at org.jfrog.hudson.pipeline.steps.DockerPushStep$Execution.run(DockerPushStep.java:105)
          at org.jfrog.hudson.pipeline.steps.DockerPushStep$Execution.run(DockerPushStep.java:62)
          at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
          at hudson.security.ACL.impersonate(ACL.java:260)
          at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
          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:1142)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

          sébastien glon added a comment - After adding Log on BuildInfoHttpFiltersSource and JenkinsBuildInfoLog, I can see than proxy received buildInfo Data But on rtDocker.push, this info is not retreived Jan 23, 2017 9:34:23 AM INFO org.jfrog.hudson.pipeline.docker.proxy.BuildInfoHttpFiltersSource filterRequest filterRequest: DefaultHttpRequest(decodeResult: success, version: HTTP/1.1) HEAD /v2/vscloud/demoapp/blobs/sha256:2c479166ffa8bfcc71460b960771b47046161ec97f8e6576da70ba202962db59 HTTP/1.1 Host: <my_artifactory_registry> User-Agent: docker/1.12.3 go/go1.6.3 git-commit/6b644ec kernel/3.10.0-327.28.3.el7.x86_64 os/linux arch/amd64 UpstreamClient(Jersey/2.23.1 (Apache HttpClient 4.5.1)) Authorization: Bearer AKCp2VobB17HMYFqxK9kcLm8jgfEbCAK8QCy7ju8q2cxnM9UvGQHhxzcDCtz2eNicvkdMGrVh Connection: close Jan 23, 2017 9:34:23 AM INFO org.jfrog.hudson.pipeline.docker.proxy.BuildInfoHttpFiltersSource filterRequest filterRequest: DefaultHttpRequest(decodeResult: success, version: HTTP/1.1) CONNECT <my_artifactory_registry>:443 HTTP/1.1 Host: <my_artifactory_registry>:443 User-Agent: Go-http-client/1.1 Jan 23, 2017 9:34:23 AM INFO org.jfrog.hudson.pipeline.docker.proxy.BuildInfoHttpFiltersSource filterRequest filterRequest: DefaultHttpRequest(decodeResult: success, version: HTTP/1.1) PUT /v2/vscloud/demoapp/manifests/dev HTTP/1.1 Host: <my_artifactory_registry> User-Agent: docker/1.12.3 go/go1.6.3 git-commit/6b644ec kernel/3.10.0-327.28.3.el7.x86_64 os/linux arch/amd64 UpstreamClient(Jersey/2.23.1 (Apache HttpClient 4.5.1)) Content-Length: 738 Authorization: Bearer AKCp2VobB17HMYFqxK9kcLm8jgfEbCAK8QCy7ju8q2cxnM9UvGQHhxzcDCtz2eNicvkdMGrVh Content-Type: application/vnd.docker.distribution.manifest.v2+json Accept-Encoding: gzip Connection: close Jan 23, 2017 9:34:23 AM INFO org.jfrog.hudson.pipeline.docker.proxy.BuildInfoFilterAdapter proxyToServerRequest Proxy message received: { "schemaVersion": 2, "mediaType": "application/vnd.docker.distribution.manifest.v2+json", "config": { "mediaType": "application/vnd.docker.container.image.v1+json", "size": 1937, "digest": "sha256:2c479166ffa8bfcc71460b960771b47046161ec97f8e6576da70ba202962db59" } , "layers": [ { "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip", "size": 668151, "digest": "sha256:56bec22e355981d8ba0878c6c2f23b21f422f30ab0aba188b54f1ffeff59c190" } , { "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip", "size": 1522511, "digest": "sha256:b94183b1beb0988d22083e5e60a94474d25be0d0dae4c57e8cb2e07a043a77be" } ] } Jan 23, 2017 9:34:23 AM INFO org.jfrog.hudson.util.JenkinsBuildInfoLog info Docker build-info found on node vscloudJenkins-731fabf61c32-host-192-168-0-54.openstacklocal : false Jan 23, 2017 9:34:23 AM INFO org.jfrog.hudson.util.JenkinsBuildInfoLog info Docker build-info found on node Jenkins : false Jan 23, 2017 9:34:23 AM WARNING org.jenkinsci.plugins.workflow.cps.CpsStepContext completed already completed CpsStepContext [34:dockerPushStep] :Owner dev-heat/demo-app/100:dev-heat/demo-app #100 java.lang.IllegalStateException: delivered here at org.jenkinsci.plugins.workflow.cps.CpsStepContext.completed(CpsStepContext.java:351) at org.jenkinsci.plugins.workflow.cps.CpsStepContext.onSuccess(CpsStepContext.java:331) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) 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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Jan 23, 2017 9:34:23 AM INFO org.jenkinsci.plugins.workflow.cps.CpsStepContext completed new success: null Jan 23, 2017 9:34:23 AM INFO org.jenkinsci.plugins.workflow.cps.CpsStepContext completed previously delivered here java.lang.Throwable at org.jenkinsci.plugins.workflow.cps.CpsStepContext.completed(CpsStepContext.java:339) at org.jenkinsci.plugins.workflow.cps.CpsStepContext.onFailure(CpsStepContext.java:327) at org.jfrog.hudson.pipeline.steps.DockerPushStep$Execution.run(DockerPushStep.java:105) at org.jfrog.hudson.pipeline.steps.DockerPushStep$Execution.run(DockerPushStep.java:62) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:260) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) 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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Jan 23, 2017 9:34:23 AM INFO org.jenkinsci.plugins.workflow.cps.CpsStepContext completed earlier failure java.lang.IllegalStateException: Build info capturing failed for docker image: docker-<my_artifactory_registry>/vscloud/demoapp:dev check build info proxy configuration. at org.jfrog.hudson.pipeline.steps.DockerPushStep$Execution.run(DockerPushStep.java:105) at org.jfrog.hudson.pipeline.steps.DockerPushStep$Execution.run(DockerPushStep.java:62) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:260) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) 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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

          A same job can sometimes works, but sometimes it failed
          this does not depend on docker-daemon all is executed on the same daemon.

          On each failed, I have this error
          Jan 23, 2017 2:55:21 PM WARNING org.jenkinsci.plugins.workflow.cps.CpsStepContext completed
          already completed CpsStepContext[35:dockerPushStep]:Ownerdev-heat/demo/master/9:dev-heat/demo/master #9
          java.lang.IllegalStateException: delivered here
          at org.jenkinsci.plugins.workflow.cps.CpsStepContext.completed(CpsStepContext.java:351)
          at org.jenkinsci.plugins.workflow.cps.CpsStepContext.onSuccess(CpsStepContext.java:331)
          at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
          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:1142)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

          sébastien glon added a comment - A same job can sometimes works, but sometimes it failed this does not depend on docker-daemon all is executed on the same daemon. On each failed, I have this error Jan 23, 2017 2:55:21 PM WARNING org.jenkinsci.plugins.workflow.cps.CpsStepContext completed already completed CpsStepContext [35:dockerPushStep] :Owner dev-heat/demo/master/9:dev-heat/demo/master #9 java.lang.IllegalStateException: delivered here at org.jenkinsci.plugins.workflow.cps.CpsStepContext.completed(CpsStepContext.java:351) at org.jenkinsci.plugins.workflow.cps.CpsStepContext.onSuccess(CpsStepContext.java:331) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) 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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

          And this info message before FAILING:

          (AWAITING_CHUNK) [id: 0xc94662c0, L:/172.18.0.2:2376 - R:/192.168.0.54:52894]: Connection to server became saturated, stopping reading
          Jan 23, 2017 3:10:57 PM INFO org.littleshoot.proxy.impl.ClientToProxyConnection serverBecameWriteable
          (AWAITING_CHUNK) [id: 0xc94662c0, L:/172.18.0.2:2376 - R:/192.168.0.54:52894]: All server connections writeable, resuming reading
          Jan 23, 2017 3:10:57 PM INFO org.littleshoot.proxy.impl.ClientToProxyConnection serverBecameSaturated
          (AWAITING_CHUNK) [id: 0xc94662c0, L:/172.18.0.2:2376 - R:/192.168.0.54:52894]: Connection to server became saturated, stopping reading
          Jan 23, 2017 3:10:57 PM INFO org.littleshoot.proxy.impl.ClientToProxyConnection serverBecameWriteable
          (AWAITING_CHUNK) [id: 0xc94662c0, L:/172.18.0.2:2376 - R:/192.168.0.54:52894]: All server connections writeable, resuming reading

          sébastien glon added a comment - And this info message before FAILING: (AWAITING_CHUNK) [id: 0xc94662c0, L:/172.18.0.2:2376 - R:/192.168.0.54:52894] : Connection to server became saturated, stopping reading Jan 23, 2017 3:10:57 PM INFO org.littleshoot.proxy.impl.ClientToProxyConnection serverBecameWriteable (AWAITING_CHUNK) [id: 0xc94662c0, L:/172.18.0.2:2376 - R:/192.168.0.54:52894] : All server connections writeable, resuming reading Jan 23, 2017 3:10:57 PM INFO org.littleshoot.proxy.impl.ClientToProxyConnection serverBecameSaturated (AWAITING_CHUNK) [id: 0xc94662c0, L:/172.18.0.2:2376 - R:/192.168.0.54:52894] : Connection to server became saturated, stopping reading Jan 23, 2017 3:10:57 PM INFO org.littleshoot.proxy.impl.ClientToProxyConnection serverBecameWriteable (AWAITING_CHUNK) [id: 0xc94662c0, L:/172.18.0.2:2376 - R:/192.168.0.54:52894] : All server connections writeable, resuming reading

          sebglon,
          We are trying to find the root cause for your issues, specifically the following message:
          Connection to server became saturated, stopping reading
          Could you share more details about your Pipeline script and the Docker image that you are pushing?

          Roman Gurevitch added a comment - sebglon , We are trying to find the root cause for your issues, specifically the following message: Connection to server became saturated, stopping reading Could you share more details about your Pipeline script and the Docker image that you are pushing?

          This error is related to FS full

          sébastien glon added a comment - This error is related to FS full

          I have been following this thread for a while as I have a similar issue.

          I receive the "Connection to server became saturated, stopping reading" as well, but do not have any full FS.. I can provide more information if needed.

          Chad Kellerman added a comment - I have been following this thread for a while as I have a similar issue. I receive the "Connection to server became saturated, stopping reading" as well, but do not have any full FS.. I can provide more information if needed.

          For further investigation please contact our support team at support@jfrog.com
          Please attach this Jira issue reference in the mail.

          Roman Gurevitch added a comment - For further investigation please contact our support team at support@jfrog.com Please attach this Jira issue reference in the mail.

          My jenkins master is on swarm cluster A

          and my slave is spawn on a second swarm cluster B.

          When i build image from my pipeline, i build on docker-in-Docker whit proxy configurer to point on my jenkins Master.

          If i check on debug, i can see buidinfo on my master but have not acces to my Docker-in-Docker and not register ImageId and Image Tag on DockerAgentUtil.registerImage method.

          Why this method check access on Docker Host?

           

          Is it possible add nodo info on BuildInfo for using them on  method updateImageParentOnAgents?

          Because my Jenkins master have buildInfo but no acces to Docker-inDocker and jenkins slave have'n buidInfo and not updateImageParent.

           

           

          sébastien glon added a comment - My jenkins master is on swarm cluster A and my slave is spawn on a second swarm cluster B. When i build image from my pipeline, i build on docker-in-Docker whit proxy configurer to point on my jenkins Master. If i check on debug, i can see buidinfo on my master but have not acces to my Docker-in-Docker and not register ImageId and Image Tag on DockerAgentUtil.registerImage method. Why this method check access on Docker Host?   Is it possible add nodo info on BuildInfo for using them on  method updateImageParentOnAgents? Because my Jenkins master have buildInfo but no acces to Docker-inDocker and jenkins slave have'n buidInfo and not updateImageParent.    

            eyalbe Eyal Ben Moshe
            as_kumlali Ali Sadik Kumlali
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: