Bug 2022321

Summary:	support for del-controller in ovs-bridges
Product:	Red Hat Enterprise Linux 9	Reporter:	Karthik Sundaravel <ksundara>
Component:	NetworkManager	Assignee:	NetworkManager Development Team <nm-team>
Status:	CLOSED NOTABUG	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	bgalvani, dsneddon, ferferna, hakhande, lrintel, rkhan, sukulkar, thaller, till
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-23 02:07:09 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 Karthik Sundaravel 2021-11-11 10:45:20 UTC

os-net-config requires "del-controller <ovs bridge>".

In the ifcfg based scripts the OVS_EXTRA parameter is used to configure the same, since the OVS_EXTRA like parameter is not available in nmcli, del-controller setting is required explicitly.

Example:
OVS_EXTRA="set bridge br-dpdk2 fail_mode=standalone -- del-controller br-dpdk2"

Comment 1 Thomas Haller 2021-11-11 20:15:51 UTC

initscritps is essentially a shell script, that invokes commands.
And  "del-controller" is a command for ovs-vsctl to perform some action.

NetworkManager is configured using profiles. Profiles are stateless descriptions of what should be configured.
As such, a profile would never have a setting with the imperative notion that "del-controller".
Instead, it could only define/describe which controller(s) should be configured (or none).


What would you think would be a suitable, descriptive way for expressing that in a connection profile (in terms of properties/settings)?

Comment 5 Dan Sneddon 2022-03-23 02:07:09 UTC

Closing as this parameter is not required for NetworkManager

Comment 6 Dan Sneddon 2022-03-23 02:08:16 UTC

This issue does not apply to NetworkManager because the bridge will be rebuilt each time NetworkManager brings up the bridge, therefore the controller will be contacted with a fresh connection.