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

cluster capabilities Build and DeploymentConfig are disabled during upgrade

    XMLWordPrintable

Details

    • Critical
    • 3
    • OTA 243
    • 1
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required

    Description

      Description of problem:

      according to enhancement a cluster resource once enabled cannot be disabled anymore. however during an upgrade of a cluster with baselineCapabilitySet:None from 4.13 to 4.14, "Build" as well as "DeploymentConfig" which are non-optional part of the cluster in 4.13, became disabled in 4.14, (where they are an optional capabilities)

      cluster version 4.13.0-0.nightly-2023-10-08-090900
      
      '.spec.capabilities'
      {
        "additionalEnabledCapabilities": [
          "NodeTuning",
          "CSISnapshot"
        ],
        "baselineCapabilitySet": "None"
      }
      
      '.status.capabilities.knownCapabilities'
      [
        "CSISnapshot",
        "Console",
        "Insights",
        "NodeTuning",
        "Storage",
        "baremetal",
        "marketplace",
        "openshift-samples"
      ]
      
      '.status.capabilities.enabledCapabilities'
      [
        "CSISnapshot",
        "NodeTuning"
      ]
       
      'ImplicitlyEnabledCapabilities'
      {
        "lastTransitionTime": "2023-10-09T17:44:54Z",
        "message": "Capabilities match configured spec",
        "reason": "AsExpected",
        "status": "False",
        "type": "ImplicitlyEnabledCapabilities"
      }
      
      
      ❯ oc get -A build
      No resources found
      
      ❯ oc get -A dc
      No resources found
      
      (rc:0, the expected output where build and dc are actually enabled)

      upgrading the cluster to 4.14 - both Build as well as DeploymentConfig expected to be ImplicitlyEnabledCapabilities as any other newly introduced capability during upgrade, however they are not:

      Requested update to release image registry.ci.openshift.org/ocp/release:4.14.0-0.nightly-2023-10-08-220853
      
      Cluster version is 4.14.0-0.nightly-2023-10-08-220853 
      
      '.status.capabilities.knownCapabilities'
      [
        "Build",
        "CSISnapshot",
        "Console",
        "DeploymentConfig",
        "ImageRegistry",
        "Insights",
        "MachineAPI",
        "NodeTuning",
        "Storage",
        "baremetal",
        "marketplace",
        "openshift-samples"
      ]
      
      '.status.capabilities.enabledCapabilities'
      [
        "CSISnapshot",
        "Console",
        "ImageRegistry",
        "MachineAPI",
        "NodeTuning"
      ]
      
      'ImplicitlyEnabledCapabilities'
      {
        "lastTransitionTime": "2023-10-09T19:08:29Z",
        "message": "The following capabilities could not be disabled: Console, ImageRegistry, MachineAPI",
        "reason": "CapabilitiesImplicitlyEnabled",
        "status": "True",
        "type": "ImplicitlyEnabledCapabilities"
      }
       

      both retrun code 1 both are disabled in the cluster as seen below:

       ❯ oc get -A build
      Error from server (NotFound): Unable to list "build.openshift.io/v1, Resource=builds": the server could not find the requested resource (get builds.build.openshift.io)
      
      ❯ oc get -A dc
      Error from server (NotFound): Unable to list "apps.openshift.io/v1, Resource=deploymentconfigs": the server could not find the requested resource (get deploymentconfigs.apps.openshift.io)
      
      

      Version-Release number of selected component (if applicable):

      upgrading from 4.13.0-0.nightly-2023-10-08-090900 to 4.14.0-0.nightly-2023-10-08-220853

      How reproducible:

      multiple times

      Steps to Reproduce:

      install 4.13 cluster with "baselineCapabilitySet": "None" and upgrade to 4.14

      Actual results:

      both previously enabled resources got disabled

      Expected results:

      capability should not disable an existing resource, but should add it to ImplicitlyEnabledCapabilities instead.

      Additional info:

       

      Attachments

        Issue Links

          Activity

            People

              trking W. Trevor King
              evakhoni@redhat.com Evgeni Vakhonin (Inactive)
              Evgeni Vakhonin Evgeni Vakhonin (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: