-
Bug
-
Resolution: Unresolved
-
Minor
-
4.18, 4.19
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
CLID Sprint 274
-
1
-
Proposed
-
Bug Fix
-
This fix addresses the duplicate release images in the collector phase of oc-mirror v2. Basically the bug fix ensures there are no duplicates.
-
None
-
None
-
None
-
None
Description of problem:
While working on https://github.com/openshift/oc-mirror/pull/1085, we noticed that during release collection, when several channels are selected for example, certain releases get copied more than once.
Version-Release number of selected component (if applicable):
4.18.0, 4.19.0
How reproducible:
always
Steps to Reproduce:
1.Use the following image set config
kind: ImageSetConfiguration
apiVersion: mirror.openshift.io/v2alpha1
mirror:
platform:
channels:
- name: stable-4.17
minVersion: 4.17.0
maxVersion: 4.17.0
- name: stable-4.16
minVersion: 4.16.0
maxVersion: 4.16.0
2. Perform a mirror to disk
3. display logs of release images collected
Actual results:
2025/03/06 10:43:41 [INFO] : 🔍 collecting release images... ✓ (9s) Collecting release quay.io/openshift-release-dev/ocp-release:4.17.0-x86_64 ✓ (10s) Collecting release quay.io/openshift-release-dev/ocp-release:4.16.0-x86_64 ✓ () Collecting release quay.io/openshift-release-dev/ocp-release:4.16.0-x86_64 ✓ (9s) Collecting release quay.io/openshift-release-dev/ocp-release:4.16.36-x86_64 ✓ () Collecting release quay.io/openshift-release-dev/ocp-release:4.17.0-x86_64
Expected results:
4.17.0-x86_64 and 4.16.0-x86_64 tags should only be "collected" once.
Additional info:
- relates to
-
CLID-182 As a oc-mirror user, I'd like a visual indication in the console log when release collection or operator collection is taking a long time
-
- Closed
-
- links to