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
- blocks
-
OCPBUGS-56563 oc-mirror v2 has no output while loading cache during disk2mirror function
-
- Closed
-
- is cloned by
-
-
- Closed
-
- links to