Bug 1812832

Description of problem:

The cluster fails to install on vSphere. It's a result of significant amount of flakes on vSphere (about 15%)

https://search.svc.ci.openshift.org/?search=Cluster+operator+machine-api+is+still+updating&maxAge=336h&context=2&type=all

Version-Release number of selected component (if applicable):

4.5-nightly

How reproducible:

15%

Steps to Reproduce:
1. Run e2e tests on vSphere in CI.

Actual results:

level=info msg="Cluster operator machine-api Progressing is True with SyncingResources: Progressing towards operator: 0.0.1-2020-03-11-155026"
level=fatal msg="failed to initialize the cluster: Cluster operator machine-api is still updating"

Expected results:

Successfully installed operator.

Additional info:

In must-gather from a cluster I found:

    - image: docker.io/openshift/origin-machine-api-operator:v4.0.0
      imageID: ""
      lastState: {}
      name: controller-manager
      ready: false
      restartCount: 0
      started: false
      state:
        waiting:
          message: |
            container create failed: time="2020-03-11T15:36:10Z" level=error msg="container_linux.go:349: starting container process caused \"exec: \\\"/manager\\\": stat /manager: no such file or directory\""
            container_linux.go:349: starting container process caused "exec: \"/manager\": stat /manager: no such file or directory"
          reason: CreateContainerError