Bug 1846451

Summary: Backport upstream CPU Manager fix 90419 [4.5.z]
Product: OpenShift Container Platform Reporter: Victor Pickard <vpickard>
Component: NodeAssignee: Artyom <alukiano>
Status: CLOSED ERRATA QA Contact: Cameron Meadors <cmeadors>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.5CC: alukiano, aos-bugs, jokerman, nagrawal, rphillips, schoudha, sjenning
Target Milestone: ---   
Target Release: 4.5.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1846428 Environment:
Last Closed: 2020-10-26 15:11:50 UTC Type: ---
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: 1846428    
Bug Blocks:    

Description Victor Pickard 2020-06-11 15:37:02 UTC
+++ This bug was initially created as a clone of Bug #1846428 +++

Description of problem:

Backport upstream fix for CPU Manager init containers 

https://github.com/kubernetes/kubernetes/pull/90419 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 12 Cameron Meadors 2020-10-20 18:41:14 UTC
cpumanager behavior is correct.  It matches y stream fix behavior with no regressions.

Comment 14 errata-xmlrpc 2020-10-26 15:11:50 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 (OpenShift Container Platform 4.5.16 bug fix 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/RHBA-2020:4268