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.
Bug 1931778 - failed to recreate VF if VF NM profiles exists
Summary: failed to recreate VF if VF NM profiles exists
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: nmstate
Version: 8.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Gris Ge
QA Contact: Mingyu Shi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-23 07:55 UTC by Mingyu Shi
Modified: 2021-11-09 20:16 UTC (History)
6 users (show)

Fixed In Version: nmstate-1.1.0-0.6.alpha6.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-09 17:42:57 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
bash.log (85.29 KB, text/plain)
2021-02-23 07:55 UTC, Mingyu Shi 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github nmstate nmstate pull 1652 0 None open SR-IOV: Fix issue when VF pre-exist before PF changes. 2021-06-25 12:10:51 UTC
Red Hat Product Errata RHBA-2021:4157 0 None None None 2021-11-09 17:43:13 UTC

Description Mingyu Shi 2021-02-23 07:55:55 UTC 
Created attachment 1758776 [details]
bash.log

Description of problem:
If NM profiles of VF instances exists, corresponding VF creation will fail at the first time. 

Version-Release number of selected component (if applicable):
nmstate-1.0.2-0.20210218100459029637.pr1520.23.g0df0f6e.el8.noarch
nispor-1.0.1-3.el8.x86_64
NetworkManager-1.30.0-0.10.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
Given PF name ens2f0
1. Use nmstate to create VF by editing ens2f0.ethernet.sr-iov.total-vfs: ens2f0v0, v1, v2...
2. Use nmstate to take ens2f0vN up(state: up)
3. Use nmstate to change PF to 'state: absent'
4. Do step 1

Actual results:
failed
  File "/usr/lib/python3.6/site-packages/libnmstate/ifaces/ifaces.py", line 656, in verify
    cur_iface.state_for_verify(),
libnmstate.error.NmstateVerificationError:
desired
=======
---
name: ens2f0v0
type: ethernet
state: down
 
current
=======
---
name: ens2f0v0
type: ethernet
state: up
ipv4:
  enabled: false
ipv6:
  enabled: false
lldp:
  enabled: false
mac-address: 7E:9D:6F:65:39:C2
mtu: 1500
 
difference
==========
--- desired
+++ current
@@ -1,4 +1,12 @@
 ---
 name: ens2f0v0
 type: ethernet
-state: down
+state: up
+ipv4:
+  enabled: false
+ipv6:
+  enabled: false
+lldp:
+  enabled: false
+mac-address: 7E:9D:6F:65:39:C2
+mtu: 1500

Expected results:
No failure

Additional info:
Comment 1 Fernando F. Mancera 2021-06-22 00:37:05 UTC 
Hi Mingyu, currently it is strange an user will need to manage the VFs of SR-IOV. I understand this is a real problem but we are out of capacity. I am closing this as WONTFIX, please re-open if this is affecting any user.

Thanks,
Fernando.
Comment 10 Mingyu Shi 2021-07-13 09:24:53 UTC 
Verified with versions:
nmstate-1.1.0-0.7.alpha7.el8.noarch
nispor-1.1.1-1.el8.x86_64
NetworkManager-1.32.2-1.el8.x86_64

Steps to Reproduce:
Given PF name ens2f0
1. Use nmstate to create VF by editing ens2f0.ethernet.sr-iov.total-vfs: ens2f0v0, v1, v2...
2. Use nmstate to take ens2f0vN up(state: up)
3. Use nmstate to change PF to 'state: absent'
4. Do step 1

Currently, after step 3, NM profiles of VF(ens2f0v*) will remain. Step 4 works well now..
Comment 13 errata-xmlrpc 2021-11-09 17:42:57 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 (nmstate 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-2021:4157
Note You need to log in before you can comment on or make changes to this bug.