-
Bug
-
Resolution: Done-Errata
-
Major
-
4.15, 4.16
-
None
-
Important
-
No
-
Sprint 252
-
1
-
Proposed
-
False
-
-
-
Bug Fix
-
Done
Description of problem:
When the user configures the install-config.yaml additionalTrustBundle field (for example, in a disconnected installation using a local registry), the user-ca-bundle configmap gets populated with more content than strictly required
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Setup a local registry and mirror the content of an ocp release 2. Configure the install-config.yaml for a mirrored installation. In particular, configure the additionalTrustBundle field with the registry cert 3. Create the agent ISO, boot the nodes and wait for the installation to complete
Actual results:
The user-ca-bundle cm does not contain onyl the registry cert
Expected results:
user-ca-bundle configmap with just the content of the install-config additionalTrustBundle field
Additional info:
- blocks
-
OCPBUGS-34721 Incorrect usage of install-config.yaml additionalTrustBundle field
- Closed
- is caused by
-
OCPBUGS-16666 Move the setting of additionalTrustBundle to InfraEnv
- Closed
- is cloned by
-
OCPBUGS-34721 Incorrect usage of install-config.yaml additionalTrustBundle field
- Closed
- is related to
-
OCPBUGS-43990 Work around excess CA certs in additionalTrustBundle
- New
- links to
-
RHEA-2024:0041 OpenShift Container Platform 4.16.z bug fix update