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

Node fails to join cluster as CSR contains wrong hostname in dualstack setup

XMLWordPrintable

    • Important
    • No
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      This is a clone of issue OCPBUGS-30139. The following is the description of the original issue:

      This is a clone of issue OCPBUGS-22324. The following is the description of the original issue:

      Description of problem:

      A node fails to join cluster as it's CSR contains incorrect hostname
      
      oc describe csr csr-7hftm
      Name:               csr-7hftm
      Labels:             <none>
      Annotations:        <none>
      CreationTimestamp:  Tue, 24 Oct 2023 10:22:39 -0400
      Requesting User:    system:serviceaccount:openshift-machine-config-operator:node-bootstrapper
      Signer:             kubernetes.io/kube-apiserver-client-kubelet
      Status:             Pending
      Subject:
               Common Name:    system:node:openshift-worker-1
               Serial Number:
               Organization:   system:nodes
      Events:  <none>
      
      oc get csr csr-7hftm -o yaml
      apiVersion: certificates.k8s.io/v1
      kind: CertificateSigningRequest
      metadata:
        creationTimestamp: "2023-10-24T14:22:39Z"
        generateName: csr-
        name: csr-7hftm
        resourceVersion: "96957"
        uid: 84b94213-0c0c-40e4-8f90-d6612fbdab58
      spec:
        groups:
        - system:serviceaccounts
        - system:serviceaccounts:openshift-machine-config-operator
        - system:authenticated
        request: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURSBSRVFVRVNULS0tLS0KTUlIN01JR2lBZ0VBTUVBeEZUQVRCZ05WQkFvVERITjVjM1JsYlRwdWIyUmxjekVuTUNVR0ExVUVBeE1lYzNsegpkR1Z0T201dlpHVTZiM0JsYm5Ob2FXWjBMWGR2Y210bGNpMHhNRmt3RXdZSEtvWkl6ajBDQVFZSUtvWkl6ajBECkFRY0RRZ0FFMjRabE1JWGE1RXRKSGgwdWg2b3RVYTc3T091MC9qN0xuSnFqNDJKY0dkU01YeTJVb3pIRTFycmYKOTFPZ3pOSzZ5Z1R0Qm16NkFOdldEQTZ0dUszMlY2QUFNQW9HQ0NxR1NNNDlCQU1DQTBnQU1FVUNJRFhHMlFVWQoxMnVlWXhxSTV3blArRFBQaE5oaXhiemJvaTBpQzhHci9kMXRBaUVBdEFDcVVwRHFLYlFUNWVFZXlLOGJPN0dlCjhqVEI1UHN1SVpZM1pLU1R2WG89Ci0tLS0tRU5EIENFUlRJRklDQVRFIFJFUVVFU1QtLS0tLQo=
        signerName: kubernetes.io/kube-apiserver-client-kubelet
        uid: c3adb2e0-6d60-4f56-a08d-6b01d3d3c065
        usages:
        - digital signature
        - client auth
        username: system:serviceaccount:openshift-machine-config-operator:node-bootstrapper
      status: {}
      

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

      4.14.0-rc.6
      

      How reproducible:

      So far only on one setup
      

      Steps to Reproduce:

      1. Deploy dualstack baremetal cluster with day1 networking with static DHCP hostnames
      2.
      3.
      

      Actual results:

      A node fails to join the cluster
      

      Expected results:

      All nodes join the cluster
      

              mkowalsk@redhat.com Mat Kowalski
              openshift-crt-jira-prow OpenShift Prow Bot
              Zhanqi Zhao Zhanqi Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: