Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 1675304[details]
System logs with NM trace enabled
Description of problem:
When activating a ethernet with SRIOV configure, the rollback triggered by failure of `min-tx-rate=1` will not remove created VFs.
Version-Release number of selected component (if applicable):
NetworkManager-1.22.8-4.el8.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Find a server with igb SRIOV ready NIC. Assuming that is ens2f0.
2. Execute:
sudo nmcli c del ens2f0
sudo nmcli c add type ethernet ifname ens2f0 \
sriov.total-vfs 1\
sriov.vfs "0 min-tx-rate=1" \
connection.autoconnect false \
connection.id ens2f0 \
ipv4.method disabled \
ipv6.method disabled
sudo nmcli c up ens2f0
ip link |grep ens2f0
Actual results:
Got left over VF `ens2f0v1`
Expected results:
The rollback should remove VFs.
Additional info:
Got `Operation not supported` in the nm.log
Comment 2Beniamino Galvani
2020-04-01 15:46:02 UTC
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/RHBA-2020:4499
Created attachment 1675304 [details] System logs with NM trace enabled Description of problem: When activating a ethernet with SRIOV configure, the rollback triggered by failure of `min-tx-rate=1` will not remove created VFs. Version-Release number of selected component (if applicable): NetworkManager-1.22.8-4.el8.x86_64 How reproducible: 100% Steps to Reproduce: 1. Find a server with igb SRIOV ready NIC. Assuming that is ens2f0. 2. Execute: sudo nmcli c del ens2f0 sudo nmcli c add type ethernet ifname ens2f0 \ sriov.total-vfs 1\ sriov.vfs "0 min-tx-rate=1" \ connection.autoconnect false \ connection.id ens2f0 \ ipv4.method disabled \ ipv6.method disabled sudo nmcli c up ens2f0 ip link |grep ens2f0 Actual results: Got left over VF `ens2f0v1` Expected results: The rollback should remove VFs. Additional info: Got `Operation not supported` in the nm.log