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.

Need ovs_extra support for DPDK configuration in nmcli
In ifcfg model, OVS_EXTRA flags are available, but not in NM

OVS_EXTRA for initscripts is a variable to pass arbitrary arguments to ovs-vsctl.

We will not add such a parameter to NetworkManager, because NetworkManager needs to understand what it is doing. That means, to understand all options and not just blindly pass on an OVS_EXTRA parameter.

Instead, please list which options are missing and should be supported. They need to be added one-by-one.

Such an RFE is welcome. Please report a different bug for them. Possibly report individual bugs, if there are individual options (as it makes sense).



Maybe, the final solution will look like an OVS_EXTRA list of parameters, but NetworkManager would still tightly control (and in parts understand) which parameters are set. Like done for OVS "external-ids". But regardless, first it needs to be understood exactly which options are to be added.

Thanks, I'll identify the required options and raise separate BZs.

(In reply to Karthik Sundaravel from comment #2)
> Thanks, I'll identify the required options and raise separate BZs.

Should we close then this BZ? Thanks!

Agreed.