New worker nodes join without `FQDN` when scaling out after upgrading to OpenShift v4.14

Issue

• After upgrading the OpenShift cluster to v4.14.16 when scaling out the nodes, the nodes join without FQDN.

  $ oc get nodes
  
  NAME                                                STATUS  ROLES         AGE   VERSION
  ip-10-XXX-XXX-XXX.example.compute.internal          Ready   infra,worker  382d  v1.27.10+c79e5e2
  ip-10-XXX-XXX-XXX.example.compute.internal          Ready   infra,worker  382d  v1.27.10+c79e5e2
  ip-10-XXX-XXX-XXX.example.compute.internal          Ready   infra,worker  382d  v1.27.10+c79e5e2
  ip-10-XXX-XXX-XXX.example.compute.internal          Ready   master        547d  v1.27.10+c79e5e2
  ip-10-XXX-XXX-XXX.example.compute.internal          Ready   master        547d  v1.27.10+c79e5e2
  ip-10-XXX-XXX-XXX.example.compute.internal          Ready   master        547d  v1.27.10+c79e5e2
  ip-10-XXX-XXX-XXX.example.compute.internal          Ready   worker        382d  v1.27.10+c79e5e2
  ip-10-XXX-XXX-XXX                                   Ready   worker        27m   v1.27.10+c79e5e2  <----
  ip-10-XXX-XXX-XXX.example.compute.internal          Ready   worker        382d  v1.27.10+c79e5e2
  ip-10-XXX-XXX-XXX                                   Ready   worker        56m   v1.27.10+c79e5e2  <----
  

• After upgrading to OpenShift v4.14.16 and scaling out the machineset, new nodes are appearing with a short name format ip-10-XXX-XXX-XXX instead of the expected complete FQDN name ip-10-XXX-XXX-XXX.example.compute.internal.

• From DHCP, the hostname is getting set to ip-10-XXX-XXX-XXX but upon querying DNS server, getting proper FQDN as the answer:

  [root@user ~]#  dig -x 10-XXX-XXX-XXX; <<>> DiG 9.11.36-RedHat-9.11.36-3.el8_6.1 <<>> -x 10-XXX-XXX-XXX
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11698
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;152.XXX.XXX.XXX.in-addr.arpa.  IN      PTR;; ANSWER SECTION:
  152.XXX.XXX.XXX.in-addr.arpa. 159 IN    PTR     ip-10-XXX-XXX-XXX.example.compute.internal.;; Query time: 0 msec
  ;; SERVER: 10.XXX.XXX.XXX#53(10.XXX.XXX.XXX)
  ;; WHEN: Wed Mar 27 12:24:38 +08 2024
  ;; MSG SIZE  rcvd: 121 
  

• EC2 instances show FQDN on the AWS console, but OpenShift CLI depicts short domain names for all newly provisioned nodes.