Can't install SNO on vSphere

4.14

100% (3 retries)

1. Install OVN SNO on vSphere 

---
 apiVersion: v1
 controlPlane:
   architecture: amd64
   hyperthreading: Enabled
   name: master
   platform:
     vsphere:
       cpus: 32
       memoryMB: 141072
       osDisk:
         diskSizeGB: 120
   replicas: 1
 compute:
 - architecture: amd64
   hyperthreading: Enabled
   name: worker
   platform:
     vsphere:
       cpus: 32
       memoryMB: 141072
       osDisk:
         diskSizeGB: 120
   replicas: 0
 metadata:
   name: skordas1101
 platform:
   vsphere:
     datacenter: DEVQEdatacenter
     defaultDatastore: vsanDatastore
     password: HIDDEN
     username: qe_user@devqe.ibmc.devcluster.openshift.com
     vCenter: vcenter.devqe.ibmc.devcluster.openshift.com
     apiVIP: 192.168.221.51
     ingressVIP: 192.168.221.53
     cluster: DEVQEcluster
     network: devqe-segment-221
 pullSecret: HIDDEN
 networking:
   clusterNetwork:
   - cidr: 10.128.0.0/14
     hostPrefix: 23
   serviceNetwork:
   - 172.30.0.0/16
   machineNetwork:
   - cidr: 192.168.221.0/24
   networkType: OVNKubernetes
 publish: External
 baseDomain: qe.devcluster.openshift.com
 sshKey: SSH-KEY

Template:

private-templates/functionality-testing/aos-4_14/ipi-on-vsphere/versioned-installer-ovn

Launcher variables:

installer_payload_image: registry.ci.openshift.org/ocp/release:4.14.0-0.nightly-2023-10-27-055157
num_masters: 1
num_workers: 0
master_worker_AllInOne: "true"
num_cpus: 32
memory: 141072
disk_size: 120
remove_bootstrap: "no" 

Installation finished with error: 

Attempted to gather debug logs after installation failure: failed to connect to the bootstrap machine: dial tcp 192.168.221.208:22: connect: connection timed out
Attempted to gather ClusterOperator status after installation failure: listing ClusterOperator objects: Get "https://api.skordas1101.qe.devcluster.openshift.com:6443/apis/config.openshift.io/v1/clusteroperators": net/http: TLS handshake timeout
Bootstrap failed to complete: timed out waiting for the condition
Failed to wait for bootstrapping to complete. This error usually happens when there is a problem with control plane hosts that prevents the control plane operators from creating the control plane.
Installation failed with error code '5'. Aborting execution.