Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-20331

previously disabled cluster capability Console unintentionally enabled during an upgrade

    XMLWordPrintable

Details

    • Yes
    • Proposed
    • False
    • Hide

      None

      Show
      None
    • Hide
      ---------- edited for release notes ----------
      * Previously, the Cluster Version Operator (CVO) enabled a capability if the existing manifest got the capability annotation after an upgrade. This caused the console to be enabled after upgrading to {product-title} 4.14 for users who had previously disabled the console capability. With this release, the unnecessary console capability was removed from the existing manifest and the console capability is no longer implicitly enabled. (link:https://issues.redhat.com/browse/OCPBUGS-20331[*OCPBUGS-20331*])
      ---------- original text ----------
      Cause: CVO automatically enables a capability if existing manifest got capability annotation after upgrade
      Consequence: users who previously disabled Console capability will have it enabled after upgrade to 4.14
      Fix: unnecessary Console capability was removed from existing manifest
      Result: Console capability is no longer implicitly enabled
      Show
      ---------- edited for release notes ---------- * Previously, the Cluster Version Operator (CVO) enabled a capability if the existing manifest got the capability annotation after an upgrade. This caused the console to be enabled after upgrading to {product-title} 4.14 for users who had previously disabled the console capability. With this release, the unnecessary console capability was removed from the existing manifest and the console capability is no longer implicitly enabled. (link: https://issues.redhat.com/browse/OCPBUGS-20331 [* OCPBUGS-20331 *]) ---------- original text ---------- Cause: CVO automatically enables a capability if existing manifest got capability annotation after upgrade Consequence: users who previously disabled Console capability will have it enabled after upgrade to 4.14 Fix: unnecessary Console capability was removed from existing manifest Result: Console capability is no longer implicitly enabled
    • Bug Fix
    • Done

    Description

      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

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-22718 previously disabled cluster capability Console unintentionally enabled during an upgrade

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is blocked by

          Spike - Represents a research-related task. OTA-1031 Impact previously disabled cluster capability Console unintentionally enabled during an upgrade

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-22718 previously disabled cluster capability Console unintentionally enabled during an upgrade

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-18326 CMO manifest lack capability annotations

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Verified
          links to

          GitHub openshift/cluster-kube-apiserver-operator#1565: OCPBUGS-20331: manifests: rename API performance dashboard

          GitHub openshift/cluster-kube-apiserver-operator#1566: OCPBUGS-20331: manifests/0000_90_kube-apiserver-operator_04_servicemonitor-apiserver: Rename to kube-apiserver-performance-recording-rules

          Web Link RHEA-2023:7198 rpm

          Activity

            People

              vrutkovs@redhat.com Vadim Rutkovsky
              evakhoni@redhat.com Evgeni Vakhonin
              Yang Yang Yang Yang
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: