The OpenShift Monitoring Team has published a set guidelines for
writing alerting rules in OpenShift, including a basic style guide.
You can find these here:
A subset of these are now being enforced in OpenShift End-to-End
tests , with temporary exceptions for existing non-compliant rules.
This component was found to have the following issues:
* Alerts without summary and/or description annotations:
Alerts MUST include summary and description annotations.
Think of summary as the first line of a commit message, or an email
subject line. It should be brief but informative. The description is
the longer, more detailed explanation of the alert.
The enhancement document linked above has examples of alerts with
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Whiteboard if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.
etcd team has not had time to review this bug but we still feel it is valid and hope to get to it in the upcoming sprints.
The LifecycleStale keyword was removed because the needinfo? flag was reset.
The bug assignee was notified.
closing this as duplicated by https://bugzilla.redhat.com/show_bug.cgi?id=2012065
a fix has been raised against https://bugzilla.redhat.com/show_bug.cgi?id=2012065
*** This bug has been marked as a duplicate of bug 2012065 ***
re-opening this for release-4.10.z
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 (OpenShift Container Platform 4.10.18 bug fix 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.