Bug 2083237

Summary:	[vsphere-ipi] Machineset scale up process delay
Product:	OpenShift Container Platform	Reporter:	Rafael Sales <rsales>
Component:	Cloud Compute	Assignee:	dmoiseev
Cloud Compute sub component:	Other Providers	QA Contact:	Milind Yadav <miyadav>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	acarlos, apizarro, dmoiseev, jorbell, laraujo, mkrejci, walters
Version:	4.9
Target Milestone:	---
Target Release:	4.11.0
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Timeout was added for vCenter client within vSphere machine controller. Lack of such timeout might led to controller blockage in case if vCenter never or very slow to respond.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-10 11:10:43 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:
Bug Depends On:
Bug Blocks:	2086104

Description Rafael Sales 2022-05-09 14:28:45 UTC

Note:
1. if you are dealing with Machines or MachineSet objects, please select the component as "Cloud Compute" under same product.
2. if you are dealing with kubelet / kubeletconfigs / container runtime configs, please select the component as "Node" under same product.

Description of problem:
When a machineset is scaled up, the time between the action and the actual virtual machine creation is too long (more than two hours). 
As the time between the machine object creation and the csr is too long, the csr is not auto approved by machine-approver since the time between the machine object creationTimestamp and csr creationTimestamp is greater than two hours.  We see that as soon the machineset is scaled up the machineset-controller detects that and triggers a new machine creation but the machine object doesn't transition to Provisioning until serveral hours later and the virtual machine is created but the entire process takes more than 8 hours


Version-Release number of MCO (Machine Config Operator) (if applicable):
4.9.24

Platform (AWS, VSphere, Metal, etc.):
Vsphere

Are you certain that the root cause of the issue being reported is the MCO (Machine Config Operator)?
(Y/N/Not sure): Not sure

How reproducible:
We can not reproducible the issue. 


Actual results:
Scale up process is delayed. 

Expected results:
scale up process is immediate to create a new machine

Comment 5 dmoiseev 2022-05-13 15:11:09 UTC

*** Bug 2065776 has been marked as a duplicate of this bug. ***

Comment 21 Milind Yadav 2022-05-19 12:38:14 UTC

Thanks Joel .

Moving to VERIFIED

Comment 23 errata-xmlrpc 2022-08-10 11:10:43 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5069