-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.18.z
-
None
Description of problem:
Version-Release number of selected component (if applicable):
Missing CLOCK_REALTIME State Propagation from TGM/GNSS Sources
- OS clock state may remain LOCKED even when timing source is unreliable
How reproducible:
Move T-GM to Holdover/Freerun and you will still see CLOCK REAL TIME in locked state
Code LocationsWorking:
example: logparser.go lines 490-507 (T-BC handling)
Missing in: logparser.go lines 591-653 (ParseGNSSLogs)
Missing in: logparser.go lines 353-411 (ParseTGMLogs)
Acknowledged TODO: metrics.go lines 255-256
Actual results:
Expected results:
When any timing source (T-BC, TGM, or GNSS) becomes unreliable:Set CLOCK_REALTIME to FREERUN
Publish ptp.OsClockSyncStateChange event
Update OS clock metricsEnsure consistent state propagation across all timing source types
Additional info:
