Bug 1768938

Summary:	Add min_tx_rate flag for SR-IOV VF in SR-IOV CNI
Product:	OpenShift Container Platform	Reporter:	Victor Pickard <vpickard>
Component:	Networking	Assignee:	Victor Pickard <vpickard>
Networking sub component:	openshift-sdn	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	zshi
Version:	4.3.0
Target Milestone:	---
Target Release:	4.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-01-23 11:11:03 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:

Description Victor Pickard 2019-11-05 15:41:13 UTC

Description of problem:

Add support for min_tx_rate flag on SR_IOV VF in SR-IOV CNI


Version-Release number of selected component (if applicable):

4.3.0


How reproducible: Always


Steps to Reproduce:
1. Openshift deployment with SR-IOV configured.
2. Deploy SR-IOV Network operator
3. Configure minTxRate in SR-IOV Network CRD.
4. Deploy pod on network configured in step 3

Actual results:
min_tx_rate not configured on VF


Expected results:
min_tx_rate configured on VF

Note: Support for min_tx_rate depends on NIC and driver. 


Additional info:

Comment 2 zhaozhanqi 2019-11-13 10:18:50 UTC

Verified this bug on quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.3.0-201911120917-ose-sriov-network-operator
 oc get crd sriovnetworks.sriovnetwork.openshift.io -o yaml | grep min
                minimum: 0
              minTxRate:
                  rate limiting). min_tx_rate should be <= max_tx_rate.
                minimum: 0
                minimum: 0
                minimum: 0

Comment 4 errata-xmlrpc 2020-01-23 11:11:03 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-2020:0062