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

NodePool not bringing up nodes due to: configmap is out of date, waiting for update 79d5ea26 != 6bd3e7f8'

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 4.14.z
    • HyperShift
    • None
    • Important
    • No
    • False
    • Hide

      None

      Show
      None

      Description of problem:

          NodePool machine instances are failing to join a HostedCluster. The nodepool status reports InvalidConfig with the following condition:
      
        - lastTransitionTime: "2024-08-07T04:57:04Z"
          message: 'Failed to generate payload: error getting ignition payload: machine-config-server
            configmap is out of date, waiting for update 79d5ea26 != 6bd3e7f8'     
          observedGeneration: 1
          reason: InvalidConfig
          status: ""
          type: ValidGeneratedPayload

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

          4.15.19 (HostedCluster)

      How reproducible:

          100%

      Steps to Reproduce:

      * Create a ROSA HCP cluster
      * Waiting for the nodepools to come up
      * Add an IdP
      * Delete ignition-server pods in the hostedcontrolplane namespace on the management cluster
      * Confirm nodepools complain about machine-config-server/token-secret hash mismatch
      * Scale down/up by deleting machine.cluster.x-k8s.io resources or otherwise     

      Actual results:

          Nodes are not created

      Expected results:

          Node is created

      Additional info:

          The workaround for the previous linked bug is not working. The machines come up provsioned but have the same error for hash mismatch

       

            Unassigned Unassigned
            ppanda.openshift Pratik Panda
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: