Why scaling up the nodes of an OCP 4.5 cluster deployed on RHV fails with DNS errors?

Issue

• Manually scaled-up a node using the web console. It is the equivalent of doing oc scale --replicas=4 machineset machineset-name_worker -n openshift-machine-api
• The result is that the node is never created. The new machine stays in provisioned and never moves to ready state. The new node never shows in the oc get nodes