-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
4.13.0
-
Critical
-
No
-
SDN Sprint 234, SDN Sprint 235
-
2
-
Rejected
-
False
-
Description of problem:
OCP 4.13.0-rc.0 on Nutanix - Trying to install with AI saas new cluster on Nutanix platform and got the following error: ovs-configuration.service got ERROR: Cannot bring up connection ovs-if-br-ex after 10 attempts
Masters were configured and finished the installation, while both workers got this error. After installation failed, restarting the ovs-configuration.service helped and configured network.
Couldn't attach logs to the bug itself so uploaded it to my drive: https://drive.google.com/drive/folders/1KP8RK4R2O7N_1wdIv0N00anOyjNCNN2p
Attached are :
1. journalctl -xe NM_CONNECTION=1a26ea01-6e9f-49f2-9bdc-fda01cf7b028 + NM_DEVICE=br-ex > jour2.txt
2. journalctl -u ovs-configuration.service > ovs-configuration.service.txt
3. journalctl > journal.txt
4. Screenshot of the configuration in AI
sos reports link - https://redhat-internal.slack.com/archives/C014N2VLTQE/p1679566179250929?thread_ts=1679557976.330119&cid=C014N2VLTQE
Version-Release number of selected component (if applicable):
How reproducible:
Not sure yet
Steps to Reproduce:
1. 2. 3.
Actual results:
at least one of the workers not getting its CNI ready, and ovs-configuration service fails
Expected results:
all workers getting their network ready and successful completion of ovs-configuration service
Additional info:
- blocks
-
COS-1926 Move RHCOS to RHEL 9.2 in OCP 4.13
- Closed
- relates to
-
OCPBUGS-10485 to install with custom instance types in some regions failed, due to network operator degraded
- Closed
- links to
-
RHEA-2023:5006 rpm