-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.14.0, 4.14.z, 4.15.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
No
-
None
-
Rejected
-
None
-
None
-
Release Note Not Required
-
N/A
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-20331. The following is the description of the original issue:
—
Description of problem:
a 4.13 cluster installed with
baselineCapabilitySet: None
additionalEnabledCapabilities: ['NodeTuning', 'CSISnapshot']
an upgrade to 4.14 causing a previously disabled Console to became ImplicitlyEnabled (in contrast with newly added 4.14 capabilities that are expected to be enabled implicitly in this case)
'ImplicitlyEnabledCapabilities'
{
"lastTransitionTime": "2023-10-09T19:08:29Z",
"message": "The following capabilities could not be disabled: Console, ImageRegistry, MachineAPI",
"reason": "CapabilitiesImplicitlyEnabled",
"status": "True",
"type": "ImplicitlyEnabledCapabilities"
}
Version-Release number of selected component (if applicable):
4.14.0-0.nightly-2023-10-08-220853
How reproducible:
100%
Steps to Reproduce:
as described above
Additional info:
the root cause appears to be https://github.com/openshift/cluster-kube-apiserver-operator/pull/1542 more info in https://redhat-internal.slack.com/archives/CB48XQ4KZ/p1696940380413289
- clones
-
OCPBUGS-20331 previously disabled cluster capability Console unintentionally enabled during an upgrade
-
- Closed
-
- is blocked by
-
OCPBUGS-20331 previously disabled cluster capability Console unintentionally enabled during an upgrade
-
- Closed
-
- is duplicated by
-
OCPBUGS-22181 [RHOCP 4.14] the capability console is automatically added
-
- Closed
-
- links to
-
RHBA-2023:6837
OpenShift Container Platform 4.14.z bug fix update