Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-17494

Event based docker push replication throws misleading 200


    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Duplicate
    • Affects Version/s: 6.3.2
    • Fix Version/s: 6.4.0
    • Component/s: Replication
    • Labels:
    • Environment:

      On premises.


      When large docker images are replicated via event-based push replication, there is a period of time on the target where not all layers are replicated, but Artifactory will return a 200 when that image is requested.  This impacts an automated build process that spans multiple sites, as the CI/users in the target region have no way of knowing when the replication is truly complete and their builds have a chance of failing.

      This is causing numerous docker image pull failures and operationally delay in our production Artifactory environments.

      Steps for reproduction:

      • Have 2 Artifactory instances, a source and target.
      • Create local Docker repositories on source and Target.
      • Set up event based push replication from Source to Target.
      • Perform a docker push of a large (1.5GB +) image to the Source Artifactory/Repository.
      • Send a docker pull request to the target repository.
      • Observe a 200 in request.log, followed by an error in docker failing to resolve the image.
        • 20180928203449|1|REQUEST||non_authenticated_user|GET|/api/docker/docker/v2/|HTTP/1.0|401|0
      • we expect the GET for the manifest to return:
        • 20180928205424|64|REQUEST||admin|GET|/api/docker/docker/v2/test/manifests/latest|HTTP/1.0|404|0
      • Wait until replication has completed, and retry the pull.  The image will successfully be downloaded.

      Suggestions for improvement:

      • Better response code when not all layers have completed replication.
      • Replication status of replications in progress (possibly with REST API) so build tools can perform a check and wait instead of failing a build.


          Issue Links



              • Assignee:
                tim.golden@bankofamerica.com Timothy Golden
              • Votes:
                0 Vote for this issue
                2 Start watching this issue


                • Created: