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

previously disabled cluster capability Console unintentionally enabled during an upgrade

XMLWordPrintable

    • 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 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

              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

                Created:
                Updated:
                Resolved: