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
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
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