Document URL: 

https://docs.openshift.com/container-platform/4.5/installing/installing_vsphere/installing-vsphere.html

https://access.redhat.com/documentation/en-us/openshift_container_platform/4.5/html/installing_on_vsphere/installing-on-vsphere#installing-vsphere

https://docs.openshift.com/container-platform/4.6/installing/installing_vsphere/installing-vsphere.html

https://access.redhat.com/documentation/en-us/openshift_container_platform/4.6/html/installing_on_vsphere/installing-on-vsphere#installing-vsphere

https://docs.openshift.com/container-platform/4.7/installing/installing_vsphere/installing-vsphere.html

https://access.redhat.com/documentation/en-us/openshift_container_platform/4.7/html/installing_on_vsphere/installing-on-vsphere#installing-vsphere

Section Number and Name: 

1.4.11. Creating Red Hat Enterprise Linux CoreOS (RHCOS) machines in vSphere
Paragraph: 
5.After the template deploys, deploy a VM for a machine in the cluster.

Describe the issue: 

Setting the "latency sensitivity" to high will lead the node scale-up process to get stuck and manual intervention will be needed to put the new node up and running within the cluster.


Suggestions for improvement: 

We should consider making a note advertising that if the optional tunable "Latency Sensitivity"  is set to High and the customer performs a node scale-up process it will get stuck because the VM will not boot. Also pointing to  https://kb.vmware.com/s/article/2002779 as the explanation and also as a workaround of this issue.

Additional information: 

based on the next threads:
https://issues.redhat.com/browse/SPLAT-38
https://bugzilla.redhat.com/show_bug.cgi?id=1918383