Comment 2 for bug 1978495

Reviewed: https://review.opendev.org/c/starlingx/monitoring/+/845645
Committed: https://opendev.org/starlingx/monitoring/commit/faa4bad91b7bc911f0f5c959906190964a51d48e
Submitter: "Zuul (22348)"
Branch: master

commit faa4bad91b7bc911f0f5c959906190964a51d48e
Author: Douglas Henrique Koerich <email address hidden>
Date: Mon Jun 13 19:39:21 2022 -0300

    Check time drift also when sampling with GM

    PHC device clock must be checked against time drifts and generate the
    proper alarm whenever minor or major thresholds are exceeded. Currently
    that check is performed only for PTP instances collecting samples using
    GNSS (when a ts2phc instance is running), but not for those using
    external GM (with ptp4l instance only), which may lead them to having
    the alarm not set. This change performs time drift checking also in the
    latter condition.

    Test Plan:
    PASS: In a lab with locked PTP, forcedly adjust PHC clock to exceed
          threshold and check for alarm raising.

    Closes-Bug: 1978495
    Signed-off-by: Douglas Henrique Koerich <email address hidden>
    Change-Id: Iea9a7b02336c997bb8fcd2692d77395ab9df765a