RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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"

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)?

Closing as this parameter is not required for NetworkManager

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.