Bug 1813411 - [4.3] Backport Upstream Topology Manager Fix 85912
Summary: [4.3] Backport Upstream Topology Manager Fix 85912
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.3.z
Assignee: Victor Pickard
QA Contact: Sunil Choudhary
URL:
Whiteboard:
Depends On: 1813410
Blocks: 1771572
TreeView+ depends on / blocked
 
Reported: 2020-03-13 17:59 UTC by Ryan Phillips
Modified: 2020-04-01 19:12 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1813410
Environment:
Last Closed: 2020-04-01 19:10:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 24688 0 None closed Bug 1813411: UPSTREAM: 85912: Fixed bug in TopologyManager with SingleNUMANode Policy 2020-03-31 14:31:04 UTC
Red Hat Product Errata RHBA-2020:0930 0 None None None 2020-04-01 19:12:14 UTC

Description Ryan Phillips 2020-03-13 17:59:06 UTC 
+++ This bug was initially created as a clone of Bug #1813410 +++

+++ This bug was initially created as a clone of Bug #1813397 +++

Description of problem:
Upstream Topology Manager fix (#85912) was not backported into 4.3

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

Version-Release number of selected component (if applicable):
4.3
4.4 and 4.5 are verified to have gotten the fix via a rebase

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 11 errata-xmlrpc 2020-04-01 19:10:46 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:0930
Note You need to log in before you can comment on or make changes to this bug.