Machine API Does Not Finish Reconciling Machine After Timeout

Machine API does not finish reconciling new machine after a timeout occurs

4.14

The timing to force the issue is difficult, but may be able to force issue with unit test injection.

1. Scale machine higher than current available
2. Have kube-apiserver / etcd timeout during period when mapi attempts to update machine info when transitioning to provisioned. 

After waiting 40+ minutes from time issue occurs, the machine never moves to provisioned even though machine vm is created.

Machine moves to provisioned state after cloning is completed.

In most cases I would agree infrastructure should be better to prevent this scenario from happening; however, CI infrastructure is going to be high at times and if we cannot recover from timeouts when attempting to progress to Provisioned, we'll have many unneeded CI failures.

This issue is not marked as high severity, but it would be great if we can improve the vsphere machine provisioning process to be able to recover from this scenario and eventually mark the machine as provisioned so the CI tests can complete.