Undefined Description of problem:
oc-mirror v2 appears to pull images during sequential runs that it does not need to pull.
Version-Release number of selected component (if applicable):
4.19.0-202509091807.p2.ge176bf6.assembly.stream.el9-e176bf6
How reproducible:
100%
Steps to Reproduce:
1.oc-mirror to disk run 1 ( imageset contains OCP release and Cincinnati operator)
2.Add compliance operator to imageset-config.yaml
3.Delete the cache registry directory
4.oc-mirror to disk run 2
Actual results:
oc mirror appears to pull images that would have already been pulled during the first mirror to disk process
Expected results:
oc mirror should not pull images that were pulled by a previous run even if they are not in the cache directory
Additional info:
In my initial testing I did not delete the cache registry between run 1 and run 2. I did see these messages below which indicate that oc mirror is trying to pull the release and cincinnati images again, even though in run 2 it shouldn't do that, and sees them in the cache.
2025/09/22 22:32:18 ^[[1;94m [INFO] ^[[0m : Success copying quay.io/openshift-release-dev/ocp-release:4.19.11-x86_64 ➡️ cache
2025/09/22 22:32:18 ^[[1;94m [INFO] ^[[0m : Success copying docker://localhost:55000/openshift/graph-image:latest ➡️ cache