Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-41331

oc-mirror count the operator catalog image twice when doing the mirror to mirror

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 4.17
    • oc-mirror
    • Moderate
    • None
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      At the moment, when using oc-mirror v2 Tech Preview, and mirroring directly to a registry (mirror to mirror workflow), the logs show the catalog images twice, which might lead the user to the conclusion that the catalog image is being mirrored twice.
      This is not the case. The catalog image is being copied once to the destination registry, and a second time to the oc-mirror local cache.
      Show
      At the moment, when using oc-mirror v2 Tech Preview, and mirroring directly to a registry (mirror to mirror workflow), the logs show the catalog images twice, which might lead the user to the conclusion that the catalog image is being mirrored twice. This is not the case. The catalog image is being copied once to the destination registry, and a second time to the oc-mirror local cache.
    • Known Issue
    • In Progress

      Description of problem:

      When doing the mirror to mirror, will count the operator catalog image twice : 
       ✓   70/81 : (3s) docker://registry.redhat.io/redhat/community-operator-index:v4.15 
       ✓   71/81 : (3s) docker://registry.redhat.io/redhat/redhat-marketplace-index:v4.15 
       ✓   72/81 : (3s) docker://registry.redhat.io/redhat/community-operator-index:v4.15 
      2024/09/06 04:55:05  [INFO]   : Mirroring is ongoing. No errors.
       ✓   73/81 : (0s) oci:///test/ibm-catalog 
       ✓   74/81 : (2s) docker://registry.redhat.io/redhat/redhat-operator-index:v4.15 
       ✓   75/81 : (2s) docker://registry.redhat.io/redhat/redhat-operator-index:v4.15 
       ✓   76/81 : (3s) docker://registry.redhat.io/redhat/redhat-operator-index:v4.14 
       ✓   77/81 : (1s) docker://registry.redhat.io/redhat/redhat-operator-index:v4.14 
       ✓   78/81 : (3s) docker://registry.redhat.io/redhat/certified-operator-index:v4.15 
       ✓   79/81 : (2s) docker://registry.redhat.io/redhat/certified-operator-index:v4.15 
       ✓   80/81 : (2s) docker://registry.redhat.io/redhat/redhat-marketplace-index:v4.15

       

      Version-Release number of selected component (if applicable):

         oc-mirror version 
      WARNING: This version information is deprecated and will be replaced with the output from --short. Use --output=yaml|json to get the full version.
      Client Version: version.Info{Major:"", Minor:"", GitVersion:"v0.0.0-unknown-7b0b3bf2", GitCommit:"7b0b3bf2", GitTreeState:"clean", BuildDate:"2024-09-06T01:32:29Z", GoVersion:"go1.23.0", Compiler:"gc", Platform:"linux/amd64"}      

      How reproducible:

           Always
          

      Steps to Reproduce:

          1. do mirror2mirror with following imagesetconfig: 
      cat config-136.yaml 
      apiVersion: mirror.openshift.io/v2alpha1
      kind: ImageSetConfiguration
      mirror:
        operators:
        - catalog: oci:///test/ibm-catalog
        - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.15
          packages:
          - name: windows-machine-config-operator
          - name: cluster-kube-descheduler-operator
        - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.14
          packages:
          - name: servicemeshoperator 
          - name: windows-machine-config-operator
        - catalog: registry.redhat.io/redhat/certified-operator-index:v4.15
          packages:
          - name: nvidia-network-operator
        - catalog: registry.redhat.io/redhat/community-operator-index:v4.15
          packages:
          - name: skupper-operator
          - name: reportportal-operator
        - catalog: registry.redhat.io/redhat/redhat-marketplace-index:v4.15
          packages:
          - name: dynatrace-operator-rhmp
      
      `oc-mirror -c config-136.yaml docker://localhost:5000/m2m06 --workspace file://m2m6 --v2  --dest-tls-verify=false`

      Actual results:

      will count the operator catalog images twice : 
      
       ✓   70/81 : (3s) docker://registry.redhat.io/redhat/community-operator-index:v4.15 
       ✓   71/81 : (3s) docker://registry.redhat.io/redhat/redhat-marketplace-index:v4.15 
       ✓   72/81 : (3s) docker://registry.redhat.io/redhat/community-operator-index:v4.15 
      2024/09/06 04:55:05  [INFO]   : Mirroring is ongoing. No errors.
       ✓   73/81 : (0s) oci:///test/ibm-catalog 
       ✓   74/81 : (2s) docker://registry.redhat.io/redhat/redhat-operator-index:v4.15 
       ✓   75/81 : (2s) docker://registry.redhat.io/redhat/redhat-operator-index:v4.15 
       ✓   76/81 : (3s) docker://registry.redhat.io/redhat/redhat-operator-index:v4.14 
       ✓   77/81 : (1s) docker://registry.redhat.io/redhat/redhat-operator-index:v4.14 
       ✓   78/81 : (3s) docker://registry.redhat.io/redhat/certified-operator-index:v4.15 
       ✓   79/81 : (2s) docker://registry.redhat.io/redhat/certified-operator-index:v4.15 
       ✓   80/81 : (2s) docker://registry.redhat.io/redhat/redhat-marketplace-index:v4.15      

      Expected results:

         Should only count the operator catalog image corretly 

      Additional info:

          

              luzuccar@redhat.com Luigi Mario Zuccarelli
              yinzhou@redhat.com ying zhou
              ying zhou ying zhou
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: