Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2035364

Summary:	NodeWithoutSDNController and similar should set a description
Product:	OpenShift Container Platform	Reporter:	W. Trevor King <wking>
Component:	Networking	Assignee:	Martin Kennelly <mkennell>
Networking sub component:	openshift-sdn	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	low
Priority:	low	CC:	ffernand
Version:	4.10
Target Milestone:	---
Target Release:	---
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-01-13 10:27:24 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 W. Trevor King 2021-12-23 18:39:51 UTC

Pointed out in CI [1]:

  : [sig-instrumentation][Late] OpenShift alerting rules should have description and summary annotations [Skipped:Disconnected] [Suite:openshift/conformance/parallel]
  Run #0: Failed	10s
  flake: Incompliant rules detected:

  Alerting rule "NodeWithoutSDNController" (group: cluster-network-operator-sdn.rules) has no 'description' annotation

Not fatal, so low priority, but looks like all the alerts in [2] need 'description' set.  Perhaps they can grow some kind of notes about likely impact on the cluster or diagnostic/mitigation ideas or some such.

[1]: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_oc/1003/pull-ci-openshift-oc-master-e2e-agnostic-cmd/1474060771901050880
[2]: https://github.com/openshift/cluster-network-operator/blob/c6ec76525bde40225a89ce8321b93c7aeaa043ab/bindata/network/openshift-sdn/alert-rules.yaml

Comment 1 Martin Kennelly 2022-01-13 10:27:24 UTC

Thank you for the BZ. This is a duplicate of: https://bugzilla.redhat.com/show_bug.cgi?id=2010361
A PR is waiting to be reviewed to fix this issue in that BZ.

*** This bug has been marked as a duplicate of bug 2010361 ***