Bug 2096315

Summary: NodeClockNotSynchronising alert's severity should be critical
Product: OpenShift Container Platform Reporter: Simon Pasquier <spasquie>
Component: MonitoringAssignee: Simon Pasquier <spasquie>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.8CC: amuller, anpicker, juzhao
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-10 11:17: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 Simon Pasquier 2022-06-13 14:08:33 UTC 
Description of problem:
The NodeClockNotSynchronising alert's severity is warning but it should be critical according to SRE-P (reason being that a de-synchronized master node can fail after TLS certificate rotation).

Version-Release number of selected component (if applicable):
4.8 (and probably before)

How reproducible:
Always

Steps to Reproduce:
1. Check alert severity in the OCP console.
2.
3.

Actual results:
Severity is warning.

Expected results:
Severity is critical.

Additional info:
https://issues.redhat.com/browse/OSD-8737
Comment 2 Junqi Zhao 2022-06-14 07:12:18 UTC 
tested with 4.11.0-0.nightly-2022-06-13-215813, NodeClockNotSynchronising now is critical alert
        - alert: NodeClockNotSynchronising
          annotations:
            description: Clock on {{ $labels.instance }} is not synchronising. Ensure NTP
              is configured on this host.
            runbook_url: https://github.com/openshift/runbooks/blob/master/alerts/cluster-monitoring-operator/NodeClockNotSynchronising.md
            summary: Clock not synchronising.
          expr: |
            min_over_time(node_timex_sync_status[5m]) == 0
            and
            node_timex_maxerror_seconds >= 16
          for: 10m
          labels:
            severity: critical
Comment 6 errata-xmlrpc 2022-08-10 11:17:24 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