Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2085413

Summary:	configure-ovs selects wrong interface on reboot
Product:	OpenShift Container Platform	Reporter:	Andreas Karis <akaris>
Component:	Networking	Assignee:	Andreas Karis <akaris>
Networking sub component:	ovn-kubernetes	QA Contact:	Anurag saxena <anusaxen>
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	high
Priority:	high	CC:	akaris, anusaxen, bnemec, cstabler, juriarte, rbrattai, rlobillo, rravaiol
Version:	4.9	Keywords:	Reopened
Target Milestone:	---
Target Release:	4.9.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2081317	Environment:
Last Closed:	2022-06-16 14:23:50 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2081317
Bug Blocks:

Comment 7 Andreas Karis 2022-06-16 14:09:33 UTC

Hi Jon,

I have a feeling that your issue might be fixed with https://github.com/openshift/machine-config-operator/pull/3183/commits/3b3e6b237c204587d30a3258b1cfadb6ec24b807

That's part of 4.9.39 (https://openshift-release.apps.ci.l2s4.p1.openshiftapps.com/releasestream/4-stable/release/4.9.39)

Can you reliably reproduce the issue on 4.9.38? In that case, can you try with 4.9.39? If it still fails with 4.9.39, can you attach the same must-gather and the node logs?

Thanks!

Comment 9 Andreas Karis 2022-06-16 14:23:50 UTC

Confirmed, you are hitting what's fixed with https://github.com/openshift/machine-config-operator/pull/3183/commits/3b3e6b237c204587d30a3258b1cfadb6ec24b807:
~~~
un 11 00:07:35.164195 ostest-bp96v-master-1 configure-ovs.sh[1268]: + nmcli -g all connection
Jun 11 00:07:35.188706 ostest-bp96v-master-1 configure-ovs.sh[1268]: br-ex:5eca00d8-85bd-4414-af25-29fb04edb275:ovs-bridge:1654906027:Sat Jun 11 00\:07\:07 2022:no:0:no:/org/freedesktop/NetworkManager/Settings/1:no:::::/etc/NetworkManage
r/systemConnectionsMerged/br-ex.nmconnection
Jun 11 00:07:35.188706 ostest-bp96v-master-1 configure-ovs.sh[1268]: ovs-if-br-ex:1bd26c3b-01a8-4c35-9429-59dd0493f029:ovs-interface:1654906027:Sat Jun 11 00\:07\:07 2022:no:0:no:/org/freedesktop/NetworkManager/Settings/2:no::::ovs-port:
/etc/NetworkManager/systemConnectionsMerged/ovs-if-br-ex.nmconnection
Jun 11 00:07:35.188706 ostest-bp96v-master-1 configure-ovs.sh[1268]: ovs-if-phys0:b7a7fa15-061e-478c-841a-de14431eded3:802-3-ethernet:1654905769:Sat Jun 11 00\:02\:49 2022:no:100:no:/org/freedesktop/NetworkManager/Settings/4:no::::ovs-po
rt:/etc/NetworkManager/systemConnectionsMerged/ovs-if-phys0.nmconnection
Jun 11 00:07:35.188706 ostest-bp96v-master-1 configure-ovs.sh[1268]: ovs-port-br-ex:b3eb3326-b1fd-467c-abd7-ce833e780bb0:ovs-port:1654906027:Sat Jun 11 00\:07\:07 2022:no:0:no:/org/freedesktop/NetworkManager/Settings/3:no::::ovs-bridge:/
etc/NetworkManager/systemConnectionsMerged/ovs-port-br-ex.nmconnection
Jun 11 00:07:35.188706 ostest-bp96v-master-1 configure-ovs.sh[1268]: ovs-port-phys0:e6bf6868-511a-41f9-866c-e74d15d91896:ovs-port:1654906027:Sat Jun 11 00\:07\:07 2022:no:0:no:/org/freedesktop/NetworkManager/Settings/5:no::::ovs-bridge:/
etc/NetworkManager/systemConnectionsMerged/ovs-port-phys0.nmconnection
~~~

this line here, the autoconnect = "no" is right after the date in the terse output:
~~~
br-ex:5eca00d8-85bd-4414-af25-29fb04edb275:ovs-bridge:1654906027:Sat Jun 11 00\:07\:07 2022:no:0:no:/org/freedesktop/NetworkManager/Settings/1:no:::::/etc/NetworkManage
~~~

I also thought about this backport again, and it still makes no sense, so I'm going to close this again ;-)