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

Control-plane upgrade blocked despite successful Nodepool upgrade in unavailable OpenShift 4.17 clusters

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 4.16, 4.17
    • HyperShift
    • None
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      Problem 

      Although 4.17 clusters are not yet available (MCE 2.6, MCE 2.7 not yet released). The customer was able to upgrade the Nodepools, but was blocked from the control-plane.

      `oc get hostedcluster <hostedcluster-name> -o jsonpath='{.status.version.availableUpdates}` 

       

      version:
          availableUpdates:
          - channels:
            - candidate-4.17
            - candidate-4.18
            - fast-4.17
            image: quay.io/openshift-release-dev/ocp-release@sha256:da1d7a184dec43c595fdf4b08387ad2a5270ce2bd7b44c68213c9b86df87c100
            url: https://access.redhat.com/errata/RHSA-2024:8229
            version: 4.17.2
          - channels:
            - candidate-4.17
            - candidate-4.18
            - fast-4.17
            - stable-4.17
            image: quay.io/openshift-release-dev/ocp-release@sha256:26c2ad974208e24a4ac

      Expected Behaviour 

      The customer should not be able to upgrade a cluster if the Control-plane for that specific version is not yet available (an older HO is in scope). 

       

      Questions: 

              rh-ee-mraee Mulham Raee
              azaalouk Adel Zaalouk
              Jie Zhao Jie Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: