Description of problem: Backport upstream CPU Manager fix 90377 https://github.com/kubernetes/kubernetes/pull/90377 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
https://github.com/openshift/origin/pull/25089 is still open
The fix will be available after the rebase on top of the k8s 1.19, no need to have the separate bug for it.
(In reply to Artyom from comment #5) > The fix will be available after the rebase on top of the k8s 1.19, no need > to have the separate bug for it. A bug is required if you plan to backport it to 4.5. Moving this bug back to MODIFIED so that it goes ON_QA automatically and the rest of the process happens.
The PR still not merged.
I missed that it 4.6 bug, so yes the fix is available after the rebase.
The fix has been backported, closing this bz.
Manually verified the code for https://github.com/kubernetes/kubernetes/pull/90377 was picked up in the rebase by visually inspecting relevant files/code in openshift/kubernetes repo on master. Also verified via visual inspection changes are in openshift/origin/vendor/k8s.io/...
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.6 GA Images), 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:4196