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

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • None
    • Rejected
    • None
    • Done
    • Known Issue
    • Hide
      Previously, when using oc-mirror v2 Technology Preview in a mirror-to-mirror workflow, logs displayed catalog images twice. This could mislead users into thinking the catalog image was mirrored twice. In reality, the image was copied once to the destination registry and once to the oc-mirror local cache. This issue has been fixed to ensure logs accurately reflect the mirroring process. (link:https://issues.redhat.com/browse/OCPBUGS-41331[*OCPBUGS-41331*])
      Show
      Previously, when using oc-mirror v2 Technology Preview in a mirror-to-mirror workflow, logs displayed catalog images twice. This could mislead users into thinking the catalog image was mirrored twice. In reality, the image was copied once to the destination registry and once to the oc-mirror local cache. This issue has been fixed to ensure logs accurately reflect the mirroring process. (link: https://issues.redhat.com/browse/OCPBUGS-41331 [* OCPBUGS-41331 *])
    • None
    • None
    • None
    • None

      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
              None
              None
              Ying Zhou Ying Zhou
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: