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.

Description of problem:

I had this test failing:
https://desktopqe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/NetworkManager/job/beaker-NetworkManager-dcb-RHEL-8.3/4/artifact/artifacts/FAIL_report_NetworkManager-dcb_Test0009_sriov_enable.html

and it was just because there was a profile created and upped for certain device.


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

How reproducible:
always

Steps to reproduce:
config deployed
[root@dell-per720-03 ~]# cat /etc/NetworkManager/conf.d/98-sriov.conf 
[device-p4p1]
match-device=interface-name:p4p1
sriov-num-vfs=63

service reload executed:
systemctl reload NetworkManager

and no p4p1_0 devices visible

Hi Thomas,

Is this even supported?
I think profile setting take priority over NetworkManager.conf.

The original test stayed the same as not failing in the latest composes and new CI test added
https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/-/merge_requests/859

NMCI's sriov_enable_with_deployed_profile passing with NetworkManager-1.36.0-0.1.el8.x86_64

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (NetworkManager bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2022:1985