Customers are unable to scale-up the OCP nodes when the initial setup is done with OCP 4.8/4.9 and then upgraded to 4.14.33/4.14.34.
The customer observed that the node scale-up failed due to fail in names resolution and noticed that the /etc/resolv.conf file does not exist on the new machines.

As a workaround, customer create the resolv.conf file manually and then it continued with setting up the new node.

During the troubleshooting we identified that the `resolv-prepender` script do not create the `resolv.conf` file due to unsupported configuration of systemd

  OCP 4.14.33, systemd 252 (252-14.el9_2.5)

    100%

    1. Install OCP in 4.9 and upgrade until 4.14.34 for instance
    2. On OCP 4.14.33/4.14.34, scale machine manually;      

Unable to scaleup node with default service definition. After manually create the /etc/resolv.conf file, scaling is working.

Node sclaing should work without making any manual changes in the node.

OCP IPI installation on Vmware