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

[v2] oc-mirror process gets killed abrutply

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • None
    • CLID Sprint 268, CLID Sprint 269
    • 2
    • Done
    • Bug Fix
    • Hide
      * Previously, when mirroring Operators using oc-mirror plugin v2, some community Operators with long lists of `skips` and `replaces` entries in their channel graphs caused the mirroring process to run out of memory and fail. With this update, oc-mirror plugin v2 improves the filtering logic by avoiding repeated evaluation of entries referenced in multiple `skips` and `replaces` stanzas, resulting in better memory handling during Operator mirroring. (link:https://issues.redhat.com/browse/OCPBUGS-52471[OCPBUGS-52471])
      Show
      * Previously, when mirroring Operators using oc-mirror plugin v2, some community Operators with long lists of `skips` and `replaces` entries in their channel graphs caused the mirroring process to run out of memory and fail. With this update, oc-mirror plugin v2 improves the filtering logic by avoiding repeated evaluation of entries referenced in multiple `skips` and `replaces` stanzas, resulting in better memory handling during Operator mirroring. (link: https://issues.redhat.com/browse/OCPBUGS-52471 [ OCPBUGS-52471 ])
    • None
    • None
    • None
    • None

      Description of problem:

      when trying to use the ImageSetConfig as described below i see that oc-mirror gets killed abruptly.
      kind: ImageSetConfiguration
      apiVersion: mirror.openshift.io/v2alpha1
      mirror:
        platform:
         channels:
         - name: stable-4.16    # Version of OpenShift to be mirrored
           minVersion: 4.16.30  # Minimum version of OpenShift to be mirrored
           maxVersion: 4.16.30  # Maximum version of OpenShift to be mirrored
           shortestPath: true
           type: ocp
         graph: true
        operators:
        - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.16
          full: false
        - catalog: registry.redhat.io/redhat/certified-operator-index:v4.16
          full: false
        - catalog: registry.redhat.io/redhat/community-operator-index:v4.16
          full: false
        helm: {}
      
          

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

           4.18
          

      How reproducible:

          Always
          

      Steps to Reproduce:

          1. Use the ImageSetConfig as above
          2. Run command `oc-mirror -c /tmp/config.yaml file://test --v2`
          3.
          

      Actual results:

          oc-mirror command gets killed even after having about 24GB of Ram and 12 core cpu, for some customers even after having 64GB of ram it looks like it never worked.
      
      2025/03/03 10:40:01  [INFO]   : :mag: collecting operator images...
      2025/03/03 10:40:01  [DEBUG]  : [OperatorImageCollector] setting copy option o.Opts.MultiArch=all when collecting operator images
      2025/03/03 10:40:01  [DEBUG]  : [OperatorImageCollector] copying operator image registry.redhat.io/redhat/redhat-operator-index:v4.16
           (24s) Collecting catalog registry.redhat.io/redhat/redhat-operator-index:v4.16 
      2025/03/03 10:40:26  [DEBUG]  : [OperatorImageCollector] manifest 2be15a52aa4978d9134dfb438e51c01b77c9585578244b97b8ba1d4f5e6c0ea1
           (5m59s) Collecting catalog registry.redhat.io/redhat/redhat-operator-index:v4.16 
      2025/03/03 10:46:01  [WARN]   : error parsing image registry.redhat.io/openshift4/ose-kube-rbac-proxy-rhel9 : registry.redhat.io/openshift4/ose-kube-rbac-proxy-rhel9 unable to parse image correctly : tag and dige ✓   (5m59s) Collecting catalog registry.redhat.io/redhat/redhat-operator-index:v4.16 
      2025/03/03 10:46:01  [DEBUG]  : [OperatorImageCollector] copying operator image registry.redhat.io/redhat/certified-operator-index:v4.16
       ⠦   (2s) Collecting catalog registry.redhat.io/redhat/certified-operator-index:v4.16 
      2025/03/03 10:46:03  [DEBUG]  : [OperatorImageCollector] manifest 816c65bcab1086e3fa158e2391d84c67cf96916027c59ab8fe44cf68a1bfe57a
      2025/03/03 10:46:03  [DEBUG]  : [OperatorImageCollector] label /configs
       ✓   (51s) Collecting catalog registry.redhat.io/redhat/certified-operator-index:v4.16 
      2025/03/03 10:46:53  [DEBUG]  : [OperatorImageCollector] copying operator image registry.redhat.io/redhat/community-operator-index:v4.16
       ⠇   (11s) Collecting catalog registry.redhat.io/redhat/community-operator-index:v4.16 
      2025/03/03 10:47:04  [DEBUG]  : [OperatorImageCollector] manifest 7a8cb7df2447b26c43b274f387197e0789c6ccc55c18b48bf0807ee00286550d
       ⠹   (34m26s) Collecting catalog registry.redhat.io/redhat/community-operator-index:v4.16 
      Killed
          

      Expected results:

           oc-mirror process should not get killed abruptly.
          

      Additional info:

          More info in the link here: https://redhat-internal.slack.com/archives/C02JW6VCYS1/p1740783474190069
          

              skhoury@redhat.com Sherine Khoury
              knarra@redhat.com Rama Kasturi Narra
              None
              Sherine Khoury
              Nidan Gavali Nidan Gavali
              None
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: