I am testing agent based installation which deploys latest 4.12

```
[root@infra workdir]# openshift-install version
openshift-install 4.12.0-0.nightly-2022-10-20-104328
built from commit 5a9ad4c024091c6658813ab3a04c8deb61d684cc
release image registry.ci.openshift.org/ocp/release@sha256:982abbcef59cf4fbbd26b7b73faa1a75d4cb4607a1ddfa0997cf445dff348104
release architecture amd64
```

On the first boot, node can take up to 15 minutes to be reachable (the static ipv4 to be assigned to br-ex)

Logs from configure-ovs
```
Oct 25 13:09:14 node-two configure-ovs.sh[2047]: + echo 'Attempt 1 to bring up connection ovs-if-phys0'                                  
Oct 25 13:09:14 node-two configure-ovs.sh[2047]: Attempt 1 to bring up connection ovs-if-phys0                                           
Oct 25 13:09:14 node-two configure-ovs.sh[2047]: + nmcli conn up ovs-if-phys0                                                            
Oct 25 13:10:44 node-two configure-ovs.sh[2525]: Error: Timeout expired (90 seconds)    

...

Oct 25 13:21:18 node-two configure-ovs.sh[2047]: + nmcli -g all connection                                                               
Oct 25 13:21:18 node-two systemd[1]: ovs-configuration.service: Succeeded.   
```

Started at 13:09 and finished at 13:21

openshift-install 4.12.0-0.nightly-2022-10-20-104328 

Almost always in my compact cluster, one of the node exhibits this behavior. I am testing in libvirt/vm based environment

1.
2.
3.

Please find attached
1. Sos report from the server
2. tar -czf /var/log/journal.tar.gz /var/log/journal
3. journactl -u {NetworkManager, ovs-configure, NetworkManager-dispatcher)