-
Bug
-
Resolution: Cannot Reproduce
-
Undefined
-
None
-
4.12.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
Rejected
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
WDescription of problem:
During testing of multi-zone vSphere installations, a problem was encountered where nodes would ignite and after pivot nodes would become unreachable. A console serial log was configured for one of the impacted nodes and it appears that `nmcli conn up ovs-if-phys0` is timing out: [ 46.194602] configure-ovs.sh[1413]: + nmcli conn up ovs-if-phys0 [ 136.090798] configure-ovs.sh[1905]: Error: Timeout expired (90 seconds)
Version-Release number of selected component (if applicable):
4.12.0-0.nightly-2022-09-08-065313
How reproducible:
consistently
Steps to Reproduce:
1. Install OpenShift on vSphere and NSX-T with OVNKubernetes 2. Control plane virtual machines will be created and ignite 3. After pivot, nodes will not indicate they have an IP for 10, sometimes 20 minutes and are unreachable
Actual results:
Nodes appear to be stuck in configure-ovs.sh
Expected results:
Nodes should be reachable able to continue to starting the kubelet
Additional info:
When installing with openshift-sdn, this behavior is not observed.
