Bug 1707027

Summary: [OSP13] Modify udev rule for VF representor rename
Product: Red Hat OpenStack Reporter: Bertrand <brault>
Component: os-net-configAssignee: RHOS Maint <rhos-maint>
Status: CLOSED ERRATA QA Contact: nlevinki <nlevinki>
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: bfournie, cfontain, fbaudin, hbrock, jslagle, mburns, pkovacs, skramaja, slinaber, waleedm, yrachman
Target Milestone: z7Keywords: OtherQA, Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: os-net-config-8.4.4-4.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-10 13:05:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1653846    

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