Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1852526

Summary:	Disable resource alignment with non-gu workload test due to failure
Product:	OpenShift Container Platform	Reporter:	Ryan Phillips <rphillips>
Component:	Node	Assignee:	Ryan Phillips <rphillips>
Status:	CLOSED ERRATA	QA Contact:	Weinan Liu <weinliu>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.6	CC:	aos-bugs, jokerman
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 16:10:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ryan Phillips 2020-06-30 15:58:36 UTC

Description of problem:

Disabling on master and possibly 4.5.

Related to https://bugzilla.redhat.com/show_bug.cgi?id=1851623

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Weinan Liu 2020-07-16 07:49:49 UTC

Bug 1851623 - [Serial][sig-node][Feature:TopologyManager] Configured cluster with non-gu workload should run with no regressions with single pod, single container requesting multiple cores [Suite:openshift/conformance/serial] consistently failing in 4.6/master 

As per comments to the BZ above https://bugzilla.redhat.com/show_bug.cgi?id=1851623#c13

This BZ is verifeid

Comment 5 errata-xmlrpc 2020-10-27 16:10:31 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.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