Bug 1768938 - Add min_tx_rate flag for SR-IOV VF in SR-IOV CNI
Summary: Add min_tx_rate flag for SR-IOV VF in SR-IOV CNI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.3.0
Assignee: Victor Pickard
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-05 15:41 UTC by Victor Pickard
Modified: 2020-01-23 11:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-23 11:11:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift sriov-cni pull 12 0 'None' 'closed' 'BUG 1768938: Add support for min_tx_rate for SR-IOV VFs' 2019-11-20 11:25:05 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:11:16 UTC

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
Note You need to log in before you can comment on or make changes to this bug.