Bug 1707027 - [OSP13] Modify udev rule for VF representor rename
Summary: [OSP13] Modify udev rule for VF representor rename
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: os-net-config
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z7
: 13.0 (Queens)
Assignee: RHOS Maint
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks: 1653846
TreeView+ depends on / blocked
 
Reported: 2019-05-06 16:27 UTC by Bertrand
Modified: 2020-11-26 14:39 UTC (History)
11 users (show)

Fixed In Version: os-net-config-8.4.4-4.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-10 13:05:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 651751 0 None MERGED Modify udev rule for VF representor rename 2020-11-26 14:16:24 UTC
OpenStack gerrit 658639 0 None MERGED Modify udev rule for VF representor rename 2020-11-26 14:16:24 UTC
Red Hat Product Errata RHBA-2019:1738 0 None None None 2019-07-10 13:05:48 UTC

Description Bertrand 2019-05-06 16:27:48 UTC 
Description of problem:
It seems that if we have more than one NIC in SR_IOV switchdev mode,
the names of the represntors will overlap for those NICS,
like pf0vf0 for the first port of the first NIC and pf0vf0 for the
first port of the second NIC, so we need to rename the VF
representor as "<sriov_pf_name>_<vf_num>" "enp3s0f0_2" in order to
be unique and consistent

Upstream Master Patch:
https://review.opendev.org/#/c/651751/
Comment 4 Waleed Mousa 2019-05-21 06:41:53 UTC 
Hi So this was fixed here https://review.opendev.org/#/c/658639/2
I think we should close this
Comment 5 Bertrand 2019-06-04 08:59:08 UTC 
Requesting blocker ack as this is required for Verizon use case (OVS HW Offload with Mellanox Cx5)
Comment 16 errata-xmlrpc 2019-07-10 13:05:27 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, 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-2019:1738
Note You need to log in before you can comment on or make changes to this bug.