-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.14.z, 4.15.z, 4.16.0, 4.17.0
-
No
-
Hypershift Sprint 254, Hypershift Sprint 255
-
2
-
False
-
-
Release Note Not Required
-
In Progress
Description of problem:
Once you registers a IDMS/ICSP which only contains the root url for the source registry, the registry-overrides is not properly filled and they are ignored. Sample: apiVersion: config.openshift.io/v1 kind: ImageDigestMirrorSet metadata: name: image-policy spec: imageDigestMirrors: - mirrors: - registry.vshiray.net/redhat.io source: registry.redhat.io - mirrors: - registry.vshiray.net/connect.redhat.com source: registry.connect.redhat.com - mirrors: - registry.vshiray.net/gcr.io source: gcr.io - mirrors: - registry.vshiray.net/docker.io source: docker.io
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. Deploy a IDMS with root registries 2. Try to deploy a Disconnected HostedCluster using the internal registry
Actual results:
The registry-overrides is empty so the disconnected deployment is stuck
Expected results:
The registry-overrides flag is properly filled and the deployment could continue
Additional info:
To workaround this, you just must create a new IDMS which points to the right OCP release version: apiVersion: config.openshift.io/v1 kind: ImageDigestMirrorSet metadata: name: ocp-release spec: imageDigestMirrors: - mirrors: - registry.vshiray.net/quay.io/openshift-release-dev/ocp-v4.0-art-dev source: quay.io/openshift-release-dev/ocp-v4.0-art-dev - mirrors: - registry.vshiray.net/quay.io/openshift-release-dev/ocp-release source: quay.io/openshift-release-dev/ocp-release
- links to
-
RHEA-2024:3718 OpenShift Container Platform 4.17.z bug fix update