This is a clone of issue OCPBUGS-55701. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-54220. The following is the description of the original issue:
—
Description of problem:
using oc-mirror 4.18.3, 4.18.4 or 4.18.5 the graph: true parameter generates an error when performing the synchronization
Version-Release number of selected component (if applicable):
4.18.3, 4.18.4 and 4.18.5
How reproducible:
Always
Steps to Reproduce:
1.create simple image set configuration file
this is my imageSetConfiguration.yaml :
---
apiVersion: mirror.openshift.io/v2alpha1
kind: ImageSetConfigurationmirror:
platform:
graph: true
kubeVirtContainer: true
architectures:
- "amd64"
channels:
- name: stable-4.18
minVersion: 4.18.2
maxVersion: 4.18.2
type: ocp
...
2.Lauch the synchronization command, this is my example :
oc-mirror.4.18.4 --v2 --authfile ${HOME}/pull-secret.txt --workspace file://${WORK_DIR}/temp --config=${WORK_DIR}/imageSetConfiguration.02.01.yaml --log-level debug --cache-dir ${WORK_DIR}/cache docker://ocpv418.registry.local
Actual results: The output is similar to : 2025/03/25 15:42:03 [INFO] : 👋 Goodbye, thank you for using oc-mirror 2025/03/25 15:42:03 [ERROR] : [ReleaseImageCollector] error processing graph image: HEAD https://ocpv418.registry.local/v2/openshift/graph-image/manifests/latest: unexpected status code 401 Unauthorized (HEAD responses have no body, use GET for details)
Expected results:
the openshift/graph-image should be uploaded correctly
Additional info:
- clones
-
OCPBUGS-55701 [v2] when oc-mirror version 4.18.3, 4.18.4 and 4.18.5 graph image synchronization generates an error
-
- Closed
-
- is blocked by
-
-
- Closed
-
- links to
-
RHBA-2025:11677
OpenShift Container Platform 4.18.21 bug fix update