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

[hypershift agent] number of active nodes - mismatch between nodepool data and cluster nodes date

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • 4.14
    • HyperShift / Agent
    • None
    • Important
    • No
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Nodepool data shows 5 CURRENT NODES, while there are 6 up and running nodes on that hosted cluster.
      
      

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

          [kni@ocp-edge119 ~]$ oc version
      Client Version: 4.14.0-0.nightly-2023-07-27-104118
      Kustomize Version: v5.0.1
      Server Version: 4.14.0-0.nightly-2023-12-09-030805
      Kubernetes Version: v1.27.8+4fab27b
      
      
      [kni@ocp-edge119 ~]$ oc get hc -A
      NAMESPACE   NAME       VERSION   KUBECONFIG                  PROGRESS    AVAILABLE   PROGRESSING   MESSAGE
      clusters    hosted-0   4.14.6    hosted-0-admin-kubeconfig   Completed   True        False         The hosted control plane is available
      [kni@ocp-edge119 ~]$ 
      
      
      

      How reproducible:

      Happens sometimes, I've seen it on over night deployment. 

      Steps to Reproduce:

          1.deploye a hub cluster + hosted cluster with 6 agent providers workers.
      I've used this job for deploying :https://auto-jenkins-csb-kniqe.apps.ocp-c1.prod.psi.redhat.com/job/CI/job/job-runner/2078/parameters/
       
          2.try to verify 6 nodes in the nodepool
          

      Actual results:

      [kni@ocp-edge119 ~]$ oc get nodepool -A NAMESPACE   NAME       CLUSTER    DESIRED NODES   CURRENT NODES   AUTOSCALING   AUTOREPAIR   VERSION   UPDATINGVERSION   UPDATINGCONFIG   MESSAGE clusters    hosted-0   hosted-0   6               5               False                      4.14.6                                       Minimum availability requires 6 replicas, current 5 available
      
      
      
      [kni@ocp-edge119 ~]$ oc get nodes --kubeconfig ~/clusterconfigs/hosted-0/auth/kubeconfig 
      NAME                STATUS   ROLES    AGE   VERSION
      hosted-worker-0-0   Ready    worker   8h    v1.27.8+4fab27b
      hosted-worker-0-1   Ready    worker   8h    v1.27.8+4fab27b
      hosted-worker-0-2   Ready    worker   8h    v1.27.8+4fab27b
      hosted-worker-0-3   Ready    worker   8h    v1.27.8+4fab27b
      hosted-worker-0-4   Ready    worker   8h    v1.27.8+4fab27b
      hosted-worker-0-5   Ready    worker   8h    v1.27.8+4fab27b
      
      
      from 'oc describe nodepool hosted-0 -n clusters':
          Observed Generation:   2
          Reason:                InstallationInProgress
          Status:                False
          Type:                  AllMachinesReady
          Last Transition Time:  2023-12-10T01:14:27Z
          Message:               Machine hosted-0-54dd8bd477xb9wfl-nsg7t: WaitingForNodeRef
      
      
      

      Expected results:

         [kni@ocp-edge119 ~]$ oc get nodepool -A NAMESPACE   NAME       CLUSTER    DESIRED NODES   CURRENT NODES   AUTOSCALING   AUTOREPAIR   VERSION   UPDATINGVERSION   UPDATINGCONFIG   MESSAGE clusters    hosted-0   hosted-0   6               6               False                      4.14.6                                      
      
      
      No related failures on 'oc describe nodepool hosted-0 -n clusters'

      Additional info:

          

            cchun@redhat.com Crystal Chun
            rhn-support-gamado Gal Amado
            Gal Amado Gal Amado
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: