Bug 1852526 - Disable resource alignment with non-gu workload test due to failure
Summary: Disable resource alignment with non-gu workload test due to failure
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.6.0
Assignee: Ryan Phillips
QA Contact: Weinan Liu
Depends On:
TreeView+ depends on / blocked
Reported: 2020-06-30 15:58 UTC by Ryan Phillips
Modified: 2020-10-27 16:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2020-10-27 16:10:31 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift origin pull 25225 0 None closed Bug 1852526: test: topology manager: temporarily disable broken tests 2020-12-08 12:06:55 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:11:08 UTC

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:

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.


Note You need to log in before you can comment on or make changes to this bug.