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

Quay was failed to mirror external image repository

XMLWordPrintable

      Description:

      This is an issue found when configure quay to mirror external image repository, after configure valid external repository mirror configurations, enable Mirror, Sync Now, get following error message.

      Mirror of 2018.03 failure to repository quayteammirror/quaydemomirror Source 'docker://quay.io/lzha/mirrordemo:2018.03' failed to sync
      Getting image source signatures
      time="2021-02-08T02:59:25Z" level=fatal msg="Error trying to reuse blob sha256:0d94e7de59b4b27051eda77847a3e1fc846797f408beefa97271f541420516c3 at destination: error pinging docker registry localhost:5000: Get \"https://localhost:5000/v2/\": dial tcp [::1]:5000: connect: connection refused"
      
      Mirror of 197e10c failure to repository quay/quayio_quay Source 'docker://quay.io/quay/quay:197e10c' failed to sync
      Getting image source signatures
      time="2021-02-08T03:19:41Z" level=fatal msg="Error trying to reuse blob sha256:f069f1d2105921f2b5520c0d1d18b04a5fe2e10f9a21afe9661cf9939c287e09 at destination: error pinging docker registry localhost:5000: Get \"https://localhost:5000/v2/\": dial tcp [::1]:5000: connect: connection refused"
      

      Index Image:

      Index image v4.7: registry-proxy.engineering.redhat.com/rh-osbs/iib:44939
      

      Quay Image:

      oc get pod
      NAME                                               READY   STATUS      RESTARTS   AGE
      quay-operator.v3.4.1-7544f7664-855r5               1/1     Running     0          39m
      quayregistry-clair-app-d78d4db75-sjmtn             1/1     Running     0          24m
      quayregistry-clair-postgres-687fdb5df7-ndfq8       1/1     Running     1          30m
      quayregistry-quay-app-55cc7b4758-kgtxf             1/1     Running     2          24m
      quayregistry-quay-config-editor-768fdd7ff7-z8pwk   1/1     Running     0          24m
      quayregistry-quay-database-6f49cf9fc5-49kwx        1/1     Running     0          23m
      quayregistry-quay-mirror-746696f4fb-76ttt          1/1     Running     0          23m
      quayregistry-quay-postgres-init-7kl9j              0/1     Completed   0          24m
      quayregistry-quay-postgres-init-9bnz4              0/1     Completed   0          30m
      quayregistry-quay-redis-6b4799b5c9-szvgj           1/1     Running     0          30m
      
      oc get pod quayregistry-quay-mirror-746696f4fb-76ttt  -o json | jq '.spec.containers[0].image'
      "registry.redhat.io/quay/quay-rhel8@sha256:bd13bb376f6547fbcb8fa64172dcc4d70d1a5e4cdeb85561784b2824f765abc6"
      
      oc get pod quayregistry-quay-app-55cc7b4758-kgtxf -o json | jq '.spec.containers[0].image'
      "registry.redhat.io/quay/quay-rhel8@sha256:bd13bb376f6547fbcb8fa64172dcc4d70d1a5e4cdeb85561784b2824f765abc6"            
      

      Steps:

      1. Deploy Quay 3.4.1 with V3.4.1 TNG Operator on AWS using AWS S3 object Storage
      2. Create new Organization
      3. Create new image repository
      4. Configure the new image repository to MIRROR State
      5. Input valid Mirror configurations to mirror from external image repository
      6. Enable Image Mirror
      7. Click Sync Now

      Expected Results:

      Quay image mirror complete successfully

      Actual Results:

      Quay image mirror was failed with error message "time="2021-02-08T03:19:41Z" level=fatal msg="Error trying to reuse blob sha256:f069f1d2105921f2b5520c0d1d18b04a5fe2e10f9a21afe9661cf9939c287e09 at destination: error pinging docker registry localhost:5000: Get \"https://localhost:5000/v2/\": dial tcp [::1]:5000: connect: connection refused""

        1. image-2021-02-18-10-47-25-728.png
          320 kB
          luffy zhang
        2. quay3341_app_pod.logs
          1.67 MB
          luffy zhang
        3. quayv341_mirror_pod.logs
          36 kB
          luffy zhang

              sleesinc Kenny Lee Sin Cheong
              lzha1981 luffy zhang
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: