Bug 2092395 - etcdHighNumberOfFailedGRPCRequests alerts with wrong results
Summary: etcdHighNumberOfFailedGRPCRequests alerts with wrong results
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd
Version: 4.11
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.11.0
Assignee: Dean West
QA Contact: ge liu
URL:
Whiteboard:
Depends On:
Blocks: 2095579
TreeView+ depends on / blocked
 
Reported: 2022-06-01 12:40 UTC by Thomas Jungblut
Modified: 2022-08-10 11:15 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 11:15:18 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-etcd-operator pull 843 0 None open Bug 2092395: etcdHighNumberOfFailedGRPCRequests alerts with wrong results 2022-06-01 13:00:13 UTC
Github openshift runbooks pull 55 0 None open Bug 2092395: Updating with latest threshold changes 2022-06-01 16:38:53 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:15:32 UTC

Description Thomas Jungblut 2022-06-01 12:40:15 UTC
etcdHighNumberOfFailedGRPCRequests does not honor the low pass filter in the denominator of the promql query. This causes the result to be matched wildly against a wrong set of grpc methods and instances and causes false positive alerts.

more info on slack: https://coreos.slack.com/archives/C0VMT03S5/p1654081131243659

Comment 6 errata-xmlrpc 2022-08-10 11:15:18 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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-2022:5069


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