-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.15.z, 4.17.z, 4.16.z, 4.18.z, 4.19.z, 4.20.z
-
None
-
None
-
False
-
-
None
-
Moderate
-
None
-
x86_64
-
Production
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
alert: NodeClockNotSynchronising is not firing on a SNO configured for RAN. This alert is and was used to trigger is the servers system-clock was out of sync with a high precision timing source. Prior to OCP 4.15 this worked for either NTP or PTP as high precision sources but 4.15 onwards this behavior has changed and it has impacted the customer negatively.
Version-Release number of selected component (if applicable):
4.18
How reproducible:
100%
Steps to Reproduce:
https://access.redhat.com/support/cases/#/case/04367385 details in this case and discussed with Telco Engineering
Actual results:
Expected results:
Additional info:
We need a way to revert the current alert back to what it was in OCP 4.14
- relates to
-
MON-3544 Adjust NodeClock* alerting rules to be inactive when the PTP operator is installed
-
- Closed
-
