Bug 1929764 - priority class scheduling conflict between user workload monitoring and in-cluster monitoring
Summary: priority class scheduling conflict between user workload monitoring and in-cl...
Keywords:
Status: CLOSED DUPLICATE of bug 1934516
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Sergiusz Urbaniak
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-17 15:36 UTC by Sergiusz Urbaniak
Modified: 2021-03-18 14:45 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-18 14:45:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Sergiusz Urbaniak 2021-02-17 15:36:01 UTC 
https://github.com/openshift/cluster-monitoring-operator/pull/1062
and
https://github.com/openshift/cluster-monitoring-operator/pull/1063

set priority classes equal to user workload monitoring (openshift-user-critical).

This can lead to unpredicted scheduling behavior during upgrades between in-cluster monitoring and user workload monitoring.
Comment 2 Simon Pasquier 2021-03-18 14:45:57 UTC 

*** This bug has been marked as a duplicate of bug 1934516 ***
Note You need to log in before you can comment on or make changes to this bug.