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