Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-9877

"Last Pulled" and "Pull Count" do not update when image pull by digest

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • None
    • quay-v3.16.0
    • quay
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False

      Description:

      "Last Pulled" and "Pull Count" columns value keep empty when pull image by digest, 

      per PROJQUAY-8414

      • for each individual image tag, Quay also maintains a pull count the associated manifest and incrmeents it on pull via tag or pull via digest

      Quay: stable-3-16-v4-19

       

      Steps:

      1. Create org/repo, and push a image tag eg. redis
      2. Pull the tag by digest
      3. Wait & Check Pull Count on UI   

      Result:

       

      - Last Pulled: Never
      - Pull Count: 0
      

       

      $ podman pull quayregistry-quay-quay-enterprise-15546.apps.quaytest-15546.qe.devcluster.openshift.com/quayorg/quayrepo@sha256:cfdb19c8fdc4b5ff3f5ed39b6958b1ac6aab0d41a39b00b15eafa9f3dab4e405 --tls-verify=false
      Trying to pull quayregistry-quay-quay-enterprise-15546.apps.quaytest-15546.qe.devcluster.openshift.com/quayorg/quayrepo@sha256:cfdb19c8fdc4b5ff3f5ed39b6958b1ac6aab0d41a39b00b15eafa9f3dab4e405...
      Getting image source signatures
      Copying blob 4b1af1e50cdb skipped: already exists 
      Copying blob cd01f30719aa skipped: already exists 
      Copying blob f93b7d3396c2 skipped: already exists 
      Copying blob b4d7ca9459fa skipped: already exists 
      Copying blob a8576e02a11b skipped: already exists 
      Copying blob 35674bc8d630 skipped: already exists 
      Copying config 53aa81e8ad done   | 
      Writing manifest to image destination
      53aa81e8adfa939348cd4c846c0ab682b16dc7641714e36bfc57b764f0b947dc

      Quay Config:  

      FEATURE_IMAGE_PULL_STATS: true
      REDIS_FLUSH_INTERVAL_SECONDS: 30
      PULL_METRICS_REDIS:
          host: quayregistry-quay-redis
          port: 6379
          db: 1

      Conclusion:

      The pullstatsredisflushworker never found your digest pull event in Redis because the digest pull was never written to Redis in the first place. Only the tag pull was recorded. 

              rhn-support-bpratt Brady Pratt
              szhao@redhat.com Sean Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: