-
Bug
-
Resolution: Done-Errata
-
Critical
-
None
-
4.16.0
-
None
Description of problem:
If I use custom CVO capabilities via the install config, I can create a capability set that disables the Ingress capability. However, once the cluster boots up, the Ingress capability will always be enabled. This creates a dissonance between the desired install config and what happens. It would be better to fail the install at install-config validation to prevent that dissonance.
Version-Release number of selected component (if applicable):
4.16
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- is cloned by
-
OCPBUGS-33794 Cluster Install with disabled Ingress capability does not disable Ingress
- Closed
- is depended on by
-
OCPBUGS-33794 Cluster Install with disabled Ingress capability does not disable Ingress
- Closed
- is related to
-
OCPBUGS-38652 [install] Documentation does not indicate the Ingress capability is always required
- New
-
OCPBUGS-41971 OCP release notes minor issue
- POST
- relates to
-
OCPBUGS-35250 Cluster-bot cannot launch `no-capabilities` clusters
- New
- links to
-
RHEA-2024:3718 OpenShift Container Platform 4.17.z bug fix update
- mentioned on