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

NodePool creation causes hypershift-operator crash

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      When creating a NodePool using a YAML manifest for a Hosted Cluster, the hypershift-operator pod crashes with an error indicating that the referenced HostedCluster object is not found.
      

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

          4.18

      How reproducible:

      100%    

      Steps to Reproduce:

      Creating nodepool using the YAML manifest for Hosted Cluster makes the hypershift-operator pod crash:
      ~~~
      $oc logs operator-b6bb4684f-zmp9g -n hypershift{"level":"info","ts":"2025-04-11T11:19:19Z","msg":"Reconciling","controller":"nodepool","controllerGroup":"hypershift.openshift.io","controllerKind":"NodePool","NodePool":{"name":"hosted-ipv4","namespace":"hcp-agent"},"namespace":"hcp-agent","name":"hosted-ipv4","reconcileID":"7acaa63f-f34b-4911-a326-dd55886df215"}
      {"level":"error","ts":"2025-04-11T11:19:19Z","msg":"Reconciler error","controller":"nodepool","controllerGroup":"hypershift.openshift.io","controllerKind":"NodePool","NodePool":{"name":"hosted-ipv4","namespace":"hcp-agent"},"namespace":"hcp-agent","name":"hosted-ipv4","reconcileID":"7acaa63f-f34b-4911-a326-dd55886df215","error":"HostedCluster.hypershift.openshift.io \"dpateriy-hcp\" not found","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:324\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:261\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:222"}
      
      $ oc get nodepool -A
      NAMESPACE   NAME          CLUSTER        DESIRED NODES   CURRENT NODES   AUTOSCALING   AUTOREPAIR   VERSION   UPDATINGVERSION   UPDATINGCONFIG   MESSAGE
      hcp-agent   hosted-ipv4   dpateriy-hcp   2
      
      $ oc get hostedcluster -A
      NAMESPACE       NAME           VERSION   KUBECONFIG                      PROGRESS   AVAILABLE   PROGRESSING   MESSAGE
      hcp-namespace   dpateriy-hcp             dpateriy-hcp-admin-kubeconfig   Partial    True        False         The hosted control plane is available
      ~~~
      
      

      Actual results:

      The nodepool created can't be see on the multicluster engine UI. (screenshot attached https://drive.google.com/file/d/11KnmnOLtq5sr_gq1LTmqQyJPYzI9mt1i/view?usp=drive_link)
      

      Expected results:

      The NodePool should be visible in the Multicluster Engine UI and the hypershift-operator should reconcile the nodepool.

      Additional info:

      Impact:
      
      - NodePool creation fails and causes operator instability.
      
      - UI inconsistency due to missing NodePool from the MCE console.
      
      
      MCE Must-gather attached https://drive.google.com/file/d/1QS3IWEI5qH_J3_rWQm0jM5jRPuIRqPV5/view?usp=drive_link

              Unassigned Unassigned
              rhn-support-dpateriy Divyam Pateriya
              None
              None
              Elsa Passaro Elsa Passaro
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: