Bug 1958107 - SR-IOV network operator pods should not run in best-effort QoS
Summary: SR-IOV network operator pods should not run in best-effort QoS
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.7
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: 4.9.0
Assignee: zenghui.shi
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-07 08:21 UTC by Tinashe Chipomho
Modified: 2021-10-18 17:31 UTC (History)
0 users

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-18 17:31:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift sriov-network-operator pull 524 0 None open Bug 1958107: Run SR-IOV pods in burstable QoS 2021-06-21 06:24:06 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:31:28 UTC

Comment 1 zenghui.shi 2021-05-18 03:33:16 UTC 
upstream PR: https://github.com/k8snetworkplumbingwg/sriov-network-operator/pull/128
Comment 3 zhaozhanqi 2021-07-14 04:38:44 UTC 
Verified this bug on 4.9.0-202107090514
Comment 6 errata-xmlrpc 2021-10-18 17:31: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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759
Note You need to log in before you can comment on or make changes to this bug.