Bug 1899582
Summary: | update discovery burst to reflect lots of CRDs on openshift clusters | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Simon Reber <sreber> |
Component: | Monitoring | Assignee: | Damien Grisonnet <dgrisonn> |
Status: | CLOSED ERRATA | QA Contact: | Junqi Zhao <juzhao> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 4.5 | CC: | alegrand, anpicker, erooth, kakkoyun, lcosic, pkrupa, surbania |
Target Milestone: | --- | ||
Target Release: | 4.7.0 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-02-24 15:34:22 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Simon Reber
2020-11-19 15:42:55 UTC
Thanks for the bug report, the solution makes sense. Lowered priority to medium from high, as from what I understand this does not actually have an effect on any component? It just logs a lot, that is all? Feel free to correct me! (In reply to Lili Cosic from comment #3) > Thanks for the bug report, the solution makes sense. Lowered priority to > medium from high, as from what I understand this does not actually have an > effect on any component? It just logs a lot, that is all? Feel free to > correct me! That is fine. But please make sure you fix it in timely manner or at least put in documentation/explanation to help people understand that it does not harm the environment and is only informational (client side throttling). Lowering the severity of this bug to low as it doesn't impact the use of any component of the monitoring stack. tested with 4.7.0-0.nightly-2020-12-08-141245, added many CRD's to OpenShift 4 and add workloads, no `Throttling request took **` info in cluster-monitoring-operator, and there's error with `oc get pod -A' 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633 |