Bug 1919239

Summary:	[UPI vSphere] VM settings could lead to undesired behavior when a new node is added to the cluster (scale-up)
Product:	OpenShift Container Platform	Reporter:	Roberto <rdiazgav>
Component:	Documentation	Assignee:	Vikram Goyal <vigoyal>
Status:	CLOSED DUPLICATE	QA Contact:	Xiaoli Tian <xtian>
Severity:	high	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	high
Version:	4.7	CC:	aos-bugs, jokerman, rdiazgav
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-01 06:47:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Roberto 2021-01-22 12:31:29 UTC

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

Comment 1 Vikram Goyal 2021-02-01 06:47:48 UTC


*** This bug has been marked as a duplicate of bug 1918383 ***