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

4.15 Control plane won't allow the creation of a 4.14 and lower node pool

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • 4.16.0
    • 4.15, 4.16
    • HyperShift
    • Critical
    • No
    • Hypershift Sprint 250
    • 1
    • Proposed
    • False
    • Hide

      None

      Show
      None

      Description of problem:

          4.15 control plane can't create a 4.14 node pool due to an issue with payload

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

          

      How reproducible:

          

      Steps to Reproduce:

          1. Create an Hosted Cluster in 4.15
          2. Create a Node Pool in 4.14
          3. Node pool stuck in provisioning
          

      Actual results:

          No node pool is created

      Expected results:

          Node pool is created as we support N-2 version there

      Additional info:

      Possibly linked to OCPBUGS-26757    

            [OCPBUGS-30242] 4.15 Control plane won't allow the creation of a 4.14 and lower node pool

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Critical: OpenShift Container Platform 4.16.0 bug fix and security update), and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHSA-2024:0041

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Critical: OpenShift Container Platform 4.16.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2024:0041

            He Liu added a comment -

            pstefans@redhat.com In my test, a 4.14 nodepool is still stuck in the upgrading process based on the lastest hypershift codes

            here is the related np condition:

              - lastTransitionTime: "2024-03-11T08:55:04Z"
                message: |-
                  Failed to generate payload: error getting ignition payload: failed to execute cluster-config-operator: cluster-config-operator process failed: F0311 10:14:50.141483    2349 render.go:51] problem with featuregate manifests: cannot return FeatureGate without rendered manifests 

            basic info: 

            $ oc get hc heli-test-np -n clusters
            NAME           VERSION                              KUBECONFIG                      PROGRESS    AVAILABLE   PROGRESSING   MESSAGE
            heli-test-np   4.16.0-0.nightly-2024-03-09-094904   heli-test-np-admin-kubeconfig   Completed   True        False         The hosted control plane is available
            
            $ hypershift create nodepool aws --name=heli-test --cluster-name=heli-test-np --node-count=1 --release-image=registry.ci.openshift.org/ocp/release:4.14.0-0.nightly-2024-03-07-200645 --namespace=clusters
            
            $ oc get np -n clusters
            NAME                      CLUSTER        DESIRED NODES   CURRENT NODES   AUTOSCALING   AUTOREPAIR   VERSION                              UPDATINGVERSION   UPDATINGCONFIG   MESSAGE
            heli-test                 heli-test-np   1                               False         False                                             True              True             Minimum availability requires 1 replicas, current 0 available
            heli-test-np-us-east-2a   heli-test-np   1               1               False         False        4.16.0-0.nightly-2024-03-09-094904  
            
            $ hypershift -v
            hypershift version openshift/hypershift: 4a99cff84977e4873289d6fb8a36559526ec1763. Latest supported OCP: 4.16.0
            
            $ oc logs -n hypershift -lapp=operator --tail=-1 | head -1
            ...
            {"level":"info","ts":"2024-03-11T04:03:51Z","logger":"setup","msg":"Starting hypershift-operator-manager","version":"openshift/hypershift: 4a99cff84977e4873289d6fb8a36559526ec1763. Latest supported OCP: 4.16.0"}

            He Liu added a comment - pstefans@redhat.com  In my test, a 4.14 nodepool is still stuck in the upgrading process based on the lastest hypershift codes here is the related np condition:   - lastTransitionTime: "2024-03-11T08:55:04Z"     message: |-       Failed to generate payload: error getting ignition payload: failed to execute cluster-config- operator : cluster-config- operator process failed: F0311 10:14:50.141483    2349 render.go:51] problem with featuregate manifests: cannot return FeatureGate without rendered manifests basic info:  $ oc get hc heli-test-np -n clusters NAME           VERSION                              KUBECONFIG                      PROGRESS    AVAILABLE   PROGRESSING   MESSAGE heli-test-np   4.16.0-0.nightly-2024-03-09-094904   heli-test-np-admin-kubeconfig   Completed   True        False         The hosted control plane is available $ hypershift create nodepool aws --name=heli-test --cluster-name=heli-test-np --node-count=1 --release-image=registry.ci.openshift.org/ocp/release:4.14.0-0.nightly-2024-03-07-200645 --namespace=clusters $ oc get np -n clusters NAME                      CLUSTER        DESIRED NODES   CURRENT NODES   AUTOSCALING   AUTOREPAIR   VERSION                              UPDATINGVERSION   UPDATINGCONFIG   MESSAGE heli-test                 heli-test-np   1                               False         False                                             True              True             Minimum availability requires 1 replicas, current 0 available heli-test-np-us-east-2a   heli-test-np   1               1               False         False        4.16.0-0.nightly-2024-03-09-094904  $ hypershift -v hypershift version openshift/hypershift: 4a99cff84977e4873289d6fb8a36559526ec1763. Latest supported OCP: 4.16.0 $ oc logs -n hypershift -lapp= operator --tail=-1 | head -1 ... { "level" : "info" , "ts" : "2024-03-11T04:03:51Z" , "logger" : "setup" , "msg" : "Starting hypershift- operator -manager" , "version" : "openshift/hypershift: 4a99cff84977e4873289d6fb8a36559526ec1763. Latest supported OCP: 4.16.0" }

            Hi pstefans@redhat.com,

            Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            OpenShift Jira Bot added a comment - Hi pstefans@redhat.com , Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            Andrea Decorte mentioned this issue in a merge request of Service Delivery / uhc-clusters-service on branch OCM-6473:

            OCM-6512 | fix: block 4.14 node pools creation for 4.15 control plane < .2

            GitLab CEE Bot added a comment - Andrea Decorte mentioned this issue in a merge request of Service Delivery / uhc-clusters-service on branch OCM-6473 : OCM-6512 | fix: block 4.14 node pools creation for 4.15 control plane < .2

              pstefans@redhat.com Patryk Stefanski
              rh-ee-adecorte Andrea Decorte
              He Liu He Liu
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: