During testing of the 4 hour holdover offset stability test, chronyd started soon after gnss loss and did not wait for the ts2phc holdover period. This blocked that test from running.

I did notice that the dpll ptp_phase_status and ptp_frequency_status show holdover. phc2sys and chronyd ptp_clock_state metrics showed locked though, and chronyc tracking verifies it was active. This snapshot is included as metrics.txt in the google drive folder.

    ptp-operator.v4.18.0-202601171614

    1/1 attempts so far. will try again and update

    1. Have GM profile with ntpfailover and --ts2phc.holdover=14400 option set
    2. Simulate GNSS loss
    3. Wait shortly for holdover while chronyd starts without waiting
    

    chronyd starts before holdover time elapsed, sync-state holdover event not emitted

    chronyd does not start until the ts2phc.holdover has elapsed, sync-state holdover event emitted