Bug 2072219 - The alert "etcdGRPCRequestsSlow" fired during upgrade
Summary: The alert "etcdGRPCRequestsSlow" fired during upgrade
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd
Version: 4.10
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Emily Moss
QA Contact: ge liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-05 19:44 UTC by Hongkai Liu
Modified: 2022-09-12 09:29 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-12 09:29:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Hongkai Liu 2022-04-05 19:44:53 UTC 
Description of problem:
The alert was fired on build02 during upgrade from 4.10.6 to 4.10.8
https://coreos.slack.com/archives/CHY2E1BL4/p1649150672833739

Everything went back to normal shortly after.

I found nothing outstanding following the runbook of the alert.
https://github.com/openshift/runbooks/blob/master/alerts/cluster-etcd-operator/etcdGRPCRequestsSlow.md

My questions are:
1. Are slow etcd requests expected to happen during upgrade?
In any case, this is the must-gather.
https://coreos.slack.com/archives/CHY2E1BL4/p1649168331222259?thread_ts=1649150672.833739&cid=CHY2E1BL4


2. The condition of the alert has never last over 10m. Yet it was fired. Why?
https://coreos.slack.com/archives/CHY2E1BL4/p1649184857585639?thread_ts=1649150672.833739&cid=CHY2E1BL4



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 8 Thomas Jungblut 2022-05-11 06:47:22 UTC 
it went into 4.11 yesterday, @emoss shall we backport this to 4.10?
Note You need to log in before you can comment on or make changes to this bug.