Using IPI on AWS. When we create a new worker using a 4.1 cloud image, the "node-valid-hostname.service" service fails with this error

# systemctl status node-valid-hostname.service
× node-valid-hostname.service - Wait for a non-localhost hostname
     Loaded: loaded (/etc/systemd/system/node-valid-hostname.service; enabled; preset: disabled)
     Active: failed (Result: timeout) since Mon 2023-10-16 08:37:50 UTC; 1h 13min ago
   Main PID: 1298 (code=killed, signal=TERM)
        CPU: 330msOct 16 08:32:50 localhost.localdomain mco-hostname[1298]: waiting for non-localhost hostname to be assigned
Oct 16 08:32:50 localhost.localdomain systemd[1]: Starting Wait for a non-localhost hostname...
Oct 16 08:37:50 localhost.localdomain systemd[1]: node-valid-hostname.service: start operation timed out. Terminating.
Oct 16 08:37:50 localhost.localdomain systemd[1]: node-valid-hostname.service: Main process exited, code=killed, status=15/TERM
Oct 16 08:37:50 localhost.localdomain systemd[1]: node-valid-hostname.service: Failed with result 'timeout'.
Oct 16 08:37:50 localhost.localdomain systemd[1]: Failed to start Wait for a non-localhost hostname.


The configured hostname is:

sh-5.1# hostname
localhost.localdomain

IPI on AWS

4.15.0-0.nightly-2023-10-15-214132

Always

1. Create a machineset using a 4.1 cloud image
2. Scale the machineset to create a new worker node
3. When the worker node is added, check the hostname and the service

The "node-valid-hostname.service" is failed and the configured hostname is 

sh-5.1# hostname localhost.localdomain

No service should fail and the new worker should have a valid hostname.