Comment 5 for bug 1995014

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ptp-notification-armada-app (r/stx.6.0)

Reviewed: https://review.opendev.org/c/starlingx/ptp-notification-armada-app/+/862995
Committed: https://opendev.org/starlingx/ptp-notification-armada-app/commit/b526c992f5e8e4e2317311ddc2ee177c3019085a
Submitter: "Zuul (22348)"
Branch: r/stx.6.0

commit b526c992f5e8e4e2317311ddc2ee177c3019085a
Author: Cole Walker <email address hidden>
Date: Fri Oct 28 15:29:36 2022 -0400

    [PTP] No longer consider clockClass 7 and 135 as locked

    PTP-notification was treating clockClass values 7 and 135 as indicators
    of a locked status, which is incorrect as per ITU-T G.8275.1. This was
    resulting in ptp-notification delivering locked status to clients when
    it should instead be transitioning to holdover/freerun.

    Removed clockClass 7 and 135 from the list of valid locked clockClasses.
    PTP-notification is now able to properly transition states when these
    classes are observed.

    This cherry-pick has been ported to r/stx6.0 which required altering the
    file paths from the original commit to fit the structure on this branch.

    Test plan:
    PASS: Build and deploy image
    PASS: Verify correct state transitions when clockClass 6, 7, 135 are
    observed

    Partial-Bug: 1995014

    Signed-off-by: Cole Walker <email address hidden>
    Change-Id: If68df991c3d6555f09e19a0d11f2c71e077c2587
    (cherry picked from commit b50b361d9fd3d02f02e1f9b62bf3a00a87141a57)