Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Undefined
Fix Version/s: Logging 5.2
Affects Version/s: None
Component/s: Log Collection
Labels:
- devel_ack+

Blocked:
False
Ready:
False
Docs QE Status:
NEW
QE Status:
NEW
Release Note Text:

Hide
Before this update, Red Hat OpenShift Logging Operator pods were scheduled on CPU cores that were reserved for customer workloads on performance-optimized single-node clusters. With this update, cluster logging operator pods are scheduled on the correct CPU cores.

Show
Before this update, Red Hat OpenShift Logging Operator pods were scheduled on CPU cores that were reserved for customer workloads on performance-optimized single-node clusters. With this update, cluster logging operator pods are scheduled on the correct CPU cores.

SFDC Cases Links:
SFDC Cases Counter:

Description

The openshift/cluster-logging-operator PR #973 added annotations
required for supporting the workload partitioning feature for ocp 4.8.
However, OLM has a bug in processing the annotations (BZ 1950047).
This PR provides a workaround necessary to release the workload
partitioning in OCP 4.8.

Attachments

Issue Links

is cloned by

LOG-1517 [release-5.1] OLM bug workaround for workload partitioning (PR#1042)

Closed

relates to

LOG-1442 BZ1966561 - OLM bug workaround for workload partitioning, cherrypick 5.0

Closed

links to

openshift/cluster-logging-operator#1042: Bug 1966561: Add OLM bug workaround for workload partitioning

Original BZ

Activity

People

Assignee:: Vitaly Grinberg

Reporter:: Vitaly Grinberg

QA Contact:: Dwaine Gonyier

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 2021/06/06 5:31 AM

Updated:: 2022/03/16 3:21 PM

Resolved:: 2021/06/30 12:35 AM