In 4.20 T‑TSC / T-BC after a PTP daemon restart and locking reports T-BC-STATUS s2 (LOCKED), but Cloud Event Proxy does not emit the corresponding event.sync.ptp-status.ptp-state-change with value LOCKED. The event stream shows FREERUN and other sync/OS clock events, yet the expected LOCKED ptp-state-change is missing, causing recovery tests a time out failure.

4.20.0-202602070127    

    %100

    1.Trigger PTP Daemon restart (configuration change in the profile; Reboot).
    2.Observe daemon logs showing T-BC-STATUS s2 after the change.
    3.Observe Cloud Event Proxy does not emit ptp-state-change with LOCKED.

    ptp-state-change LOCKED event is missing after T-BC-STATUS s2 following configuration change; tests waiting for LOCKED time out.

    After configuration change, when T-BC-STATUS s2 is observed, Cloud Event Proxy should emit event.sync.ptp-status.ptp-state-change with value LOCKED.