-
Bug
-
Resolution: Can't Do
-
Major
-
None
-
4.18
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
While mirroring IBM Business Automation for channel: 8.x-stable and version 8.0.6-1 fails for a one image:
registry.redhat.io/openshift4/ose-oauth-proxy@sha256:ac9c6aa05cd88cb10c46f3d018ffec42868f6909633fbbd75ad1ddc70dacaf7c
Version-Release number of selected component (if applicable):
How reproducible:
oc-mirror -c imagesetconfig-4-18-bmoe.yaml --workspace file:///<File_Path> docker://<Registry_URL> --v2 --image-timeout 60m0s -p 550022025/06/20 08:35:16 [ERROR] : [Worker] error mirroring image docker://registry.redhat.io/openshift4/ose-oauth-proxy@sha256:ac9c6aa05cd88cb10c46f3d018ffec42868f6909633fbbd75ad1ddc70dacaf7c (Operator bundles: [bamoe-businessautomation-operator.8.0.6-1] - Operators: [bamoe-businessautomation-operator]) error: initializing source docker://registry.redhat.io/openshift4/ose-oauth-proxy@sha256:ac9c6aa05cd88cb10c46f3d018ffec42868f6909633fbbd75ad1ddc70dacaf7c: reading manifest sha256:ac9c6aa05cd88cb10c46f3d018ffec42868f6909633fbbd75ad1ddc70dacaf7c in registry.redhat.io/openshift4/ose-oauth-proxy: manifest unknown
Steps to Reproduce:
1. Create Image-set Configuration apiVersion: mirror.openshift.io/v2alpha1 kind: ImageSetConfiguration archiveSize: 25 mirror: operators: - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.18 targetCatalog: redhat/redhat-operators targetTag: 'v4.18.17' packages: - name: bamoe-businessautomation-operator channels: - name: 8.x-stable minVersion: '8.0.6-1' 2. oc-mirror -c imagesetconfig-4-18-bmoe.yaml file:///<File_Path> --v2 -p 55001 3. oc-mirror -c imagesetconfig-4-18-bmoe.yaml file:///<File_Path> --v2 19:29:34 [INFO] : === Results === 2025/06/19 19:29:34 [INFO] : ✗ 77 / 79 operator images mirrored: Some operator images failed to be mirrored - please check the logs 2025/06/19 19:29:34 [ERROR] : [Worker] error mirroring image docker://registry.redhat.io/openshift4/ose-oauth-proxy@sha256:ac9c6aa05cd88cb10c46f3d018ffec42868f6909633fbbd75ad1ddc70dacaf7c (Operator bundles: [bamoe-businessautomation-operator.8.0.6-1] - Operators: [bamoe-businessautomation-operator]) error: initializing source docker://registry.redhat.io/openshift4/ose-oauth-proxy@sha256:ac9c6aa05cd88cb10c46f3d018ffec42868f6909633fbbd75ad1ddc70dacaf7c: reading manifest sha256:ac9c6aa05cd88cb10c46f3d018ffec42868f6909633fbbd75ad1ddc70dacaf7c in registry.redhat.io/openshift4/ose-oauth-proxy: manifest unknown 2025/06/19 19:29:34 [ERROR] : [Worker] error mirroring image docker://registry.redhat.io/ibm-bamoe/bamoe-operator-bundle@sha256:da4ab08f0ac23a3d12b73398b0e5b0ec35ed4f19ee6620e4b2615633f5a8ae41 error: skipping operator bundle docker://registry.redhat.io/ibm-bamoe/bamoe-operator-bundle@sha256:da4ab08f0ac23a3d12b73398b0e5b0ec35ed4f19ee6620e4b2615633f5a8ae41 because one of its related images failed to mirror 2025/06/19 19:29:34 [INFO] : 📦 Preparing the tarball archive...
Actual results:
The Image is missing from the operator package in the RedHat registry.
Expected results:
The operator image should be present in the registry to complete the mirroring.
Additional info:
