-
Bug
-
Resolution: Done
-
Undefined
-
4.19.0, 4.20.0
-
None
Description of problem:
ClusterVersion: The condition type is changed from "ImplicitlyEnabledCapabilities" to "ImplicitlyEnabled"
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Launch a 4.19/4.20 clulster
2. Configure cv.spec.capabilities.baselineCapabilitySet=None.
3. Check the clusterversion/version object on the cluster.
Actual results:
# ./oc get clusterversion/version -ojson | jq -r '.status.conditions[]|select(.type=="ImplicitlyEnabled")'
{
"lastTransitionTime": "2025-05-12T10:07:25Z",
"message": "The following capabilities could not be disabled: Ingress, OperatorLifecycleManager",
"reason": "CapabilitiesImplicitlyEnabled",
"status": "True",
"type": "ImplicitlyEnabled"
}
Expected results:
"type": "ImplicitlyEnabledCapabilities"
Additional info:
See here for more information.
- blocks
-
OCPBUGS-56771 ClusterVersion: The condition type is changed from "ImplicitlyEnabledCapabilities" to "ImplicitlyEnabled"
-
- Closed
-
- is cloned by
-
OCPBUGS-56771 ClusterVersion: The condition type is changed from "ImplicitlyEnabledCapabilities" to "ImplicitlyEnabled"
-
- Closed
-
- relates to
-
OTA-1533 pre-merge testing: Move implicit capability enablement to libary-go
-
- In Progress
-
- links to