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

oc-mirror v2 has no output while loading cache during disk2mirror function

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • CLID Sprint 271
    • 1
    • Done
    • Bug Fix
    • Hide
      * Previously, oc-mirror plugin v2 did not display any progress output during the local cache population phase. For mirror configurations involving a large number of images, this could make the process appear unresponsive or stuck.
      With this update, a progress bar has been added to provide visibility into the cache population status, for user awareness and experience. (link:https://issues.redhat.com/browse/OCPBUGS-56563[OCPBUGS-56563])
      Show
      * Previously, oc-mirror plugin v2 did not display any progress output during the local cache population phase. For mirror configurations involving a large number of images, this could make the process appear unresponsive or stuck. With this update, a progress bar has been added to provide visibility into the cache population status, for user awareness and experience. (link: https://issues.redhat.com/browse/OCPBUGS-56563 [ OCPBUGS-56563 ])
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-55966. The following is the description of the original issue:
      —
      Description of problem:

          During the disk2mirror process, oc-mirror v2 populates a cache registry but creates no log output during that process even with debug logging enabled. Populating the cache registry takes 2 hours for 300GBs of container content. This means oc-mirror v2 has no output on the CLI for 2 hours. Users see this as a stuck process.

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

      How reproducible:

          100%

      Steps to Reproduce:

          1.Run the oc-mirror v2 disk2mirror command with debug logging enabled and a decent size archive.
    2. See that there is no log output as the cache registry is populated
    3.

      Actual results:

          Ctrl-C oc-mirror because the user thinks that it is frozen, stuck, or hung.

      Expected results:

          oc-mirror has enough output during the disk2mirror cache population process that a user would not think the process is frozen, hung, or stuck

      Additional info:

          Example command and output


[ec2-user@ip-172-31-27-203 mirror]$ oc-mirror -c ./4.18.9-mirror.yaml --from file:///home/ec2-user/mirror/mirror1 docker://ip-172-31-27-203.us-gov-west-1.compute.internal:8443 --v2 

2025/05/07 02:36:42  [INFO]   : 👋 Hello, welcome to oc-mirror
2025/05/07 02:36:42  [INFO]   : ⚙️  setting up the environment for you...
2025/05/07 02:36:42  [INFO]   : 🔀 workflow mode: diskToMirror

              rdossant Rafael Fonseca dos Santos
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              None
              Nidan Gavali Nidan Gavali
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: