Bug 2010719

Summary:	etcdHighNumberOfFailedGRPCRequests runbook is missing
Product:	OpenShift Container Platform	Reporter:	Brad Ison <brad.ison>
Component:	Etcd	Assignee:	Nobody <nobody>
Status:	CLOSED ERRATA	QA Contact:	ge liu <geliu>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.10
Target Milestone:	---
Target Release:	4.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-10 16:17:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Brad Ison 2021-10-05 12:21:37 UTC

Description of problem:

I noticed the 'etcdHighNumberOfFailedGRPCRequests' alert links to a runbook that doesn't exist:

https://github.com/openshift/runbooks/blob/master/alerts/cluster-etcd-operator/etcdHighNumberOfFailedGRPCRequests.md

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

At least 4.9 and above.

How reproducible: Always


Steps to Reproduce:

1. Visit the URL in the annotation: https://github.com/openshift/cluster-etcd-operator/blob/master/manifests/0000_90_etcd-operator_03_prometheusrule.yaml#L135

Actual results:

It's a 404.

Expected results:

The runbook exists.

Additional info:

Comment 2 Lili Cosic 2021-10-07 09:54:48 UTC

This alert was only introduced in 4.10.

Comment 9 errata-xmlrpc 2022-03-10 16:17:15 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 (Moderate: OpenShift Container Platform 4.10.3 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:0056