Bug 1664797

Summary: Backport fixes for supporting NIC Partitioning in OvS 2.9
Product: Red Hat OpenStack Reporter: Karthik Sundaravel <ksundara>
Component: openvswitchAssignee: Timothy Redaelli <tredaelli>
Status: CLOSED ERRATA QA Contact: Roee Agiman <ragiman>
Severity: medium Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: apevec, ccopello, cfontain, chrisw, dcadzow, fbaudin, rhos-maint, supadhya, tredaelli, vkhitrin
Target Milestone: z5Keywords: FeatureBackport, Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openvswitch-2.9.0-93.el7fdn Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1665882 (view as bug list) Environment:
Last Closed: 2019-03-14 13:28:34 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: 1665882    
Bug Blocks:    

Description Karthik Sundaravel 2019-01-09 16:50:46 UTC 
The Below patches needs to be backported to OvS 2.9 for enabling NIC partitioning on X710 cards

1. https://github.com/openvswitch/ovs/commit/e10ca8b921020383ea6cd50804e152ff90b2aa42
2. http://mails.dpdk.org/archives/stable/2017-December/003856.html
Comment 3 Sanjay Upadhyay 2019-03-06 12:47:59 UTC 
For NFV QA, 
this bug is against the component openvswitch, it is not the the RFE about nic-partitioning and nfv-dfg need to ensure that the new version of ovs-2.9  doesn't introduce any regression.
Comment 4 Vadim Khitrin 2019-03-07 11:05:13 UTC 
Verified on a newer release of openvswitch(openvswitch-2.9.0-93.el7fdn), no regression was introduced to NFV CI.
Comment 7 errata-xmlrpc 2019-03-14 13:28:34 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:0552