Bug 1942006

Summary:	ovs-configuration.service Fails on OCP 4.7 VMware UPI Install
Product:	OpenShift Container Platform	Reporter:	Chris Keller <ckeller>
Component:	Networking	Assignee:	Tim Rozet <trozet>
Networking sub component:	ovn-kubernetes	QA Contact:	Anurag saxena <anusaxen>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	anbhat, mmahmoud
Version:	4.7	Flags:	trozet: needinfo-
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2006732 (view as bug list)		Environment:
Last Closed:	2021-03-25 16:44:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Chris Keller 2021-03-23 12:07:30 UTC

Description of problem:

OpenShift 4.7.x fails during a VMware UPI installation.


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

Tested 4.7.0-4.7.3.


How reproducible:

Always.


Steps to Reproduce:
1. Install OpenShift
2. Wait for master nodes to come up.


Actual results:

Master nodes are in a permanent NotReady state.


Expected results:

OCP cluster installs successfully. 


Additional info:

The ovs-configuration.service fails on all master nodes. Output of journalctl -u ovs-configuration.service and logs from ovnkube-node container from one of the masters is attached.

$ oc logs -n openshift-ovn-kubernetes ovnkube-node-frwtm -c ovnkube-node | tail -n 10
I0323 11:59:22.921177  600528 gateway_iptables.go:46] Chain: "nat" in table: "POSTROUTING" already exists, skipping creation
I0323 11:59:22.930810  600528 ovs.go:166] exec(8): /usr/bin/ovs-vsctl --timeout=15 -- port-to-br br-ex
I0323 11:59:22.946460  600528 ovs.go:169] exec(8): stdout: ""
I0323 11:59:22.946506  600528 ovs.go:170] exec(8): stderr: "ovs-vsctl: no port named br-ex\n"
I0323 11:59:22.946526  600528 ovs.go:172] exec(8): err: exit status 1
I0323 11:59:22.946586  600528 ovs.go:166] exec(9): /usr/bin/ovs-vsctl --timeout=15 -- br-exists br-ex
I0323 11:59:22.960816  600528 ovs.go:169] exec(9): stdout: ""
I0323 11:59:22.960857  600528 ovs.go:170] exec(9): stderr: ""
I0323 11:59:22.960873  600528 ovs.go:172] exec(9): err: exit status 2
F0323 11:59:22.961023  600528 ovnkube.go:130] failed to convert br-ex to OVS bridge: Link not found

Comment 7 Tim Rozet 2021-03-24 19:00:19 UTC

This looks the same as https://bugzilla.redhat.com/show_bug.cgi?id=1938084

Chris, can you please try with the fixes there and let me know if it works?

Comment 9 Tim Rozet 2021-03-25 16:44:39 UTC

Since we are fairly confident this is the same. I'm going to dupe and feel free to reopen if it is a different issue.

*** This bug has been marked as a duplicate of bug 1938084 ***