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

'oc adm upgrade channel ...' should not clobber unrecognized spec properties

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • 4.9
    • oc
    • None
    • Moderate
    • No
    • 3
    • OTA 232
    • 1
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      4.9 and 4.10 oc calls to oc adm upgrade channel ... for 4.11+ clusters would clear spec.capabilities. Not all that many clusters try to restrict capabilities, but folks will need to bump their channel for at least every other minor (if their using EUS channels), and while we recommend folks use an oc from the 4.y they're heading towards, we don't have anything in place to enforce that.

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

      4.9 and 4.10 oc are exposed vs. the new-in-4.11 spec.capabilities. Newer oc could theoretically be exposed vs. any new ClusterVersion spec capabilities.

      How reproducible:

      100%

      Steps to Reproduce:

      1. Install a 4.11+ cluster with None capabilities.
      2. Set the channel with a 4.10.51 oc, like oc adm upgrade channel fast-4.11.
      3. Check the capabilities with oc get -o json clusterversion version | jq -c .spec.capabilities.

      Actual results:

      null
      

      Expected results:

      {"baselineCapabilitySet":"None"}
      

            trking W. Trevor King
            trking W. Trevor King
            ying zhou ying zhou
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: