Very high ts2phc offsets reported in linuxptp log while metrics show ts2phc clock_state is locked and GM clock_state is FREERUN

    ptp-operator.v4.15.0-202407021637

    100%

    1. Deploy 4.15 SNO with GM ptpconfig
    2. Check metrics for clock_state
    3. Check linuxptp-daemon log for ts2phc offset
    

NAMESPACE       NAME               AGE
openshift-ptp   du-ptp-slave-gm1   42m
openshift-ptp   du-ptp-slave-gm2   42m
openshift-ptp   grandmaster1       42m

ts2phc[4116.338]: [ts2phc.2.config] ens7f0 extts index 0 at 1720011075.040044361 corr 0 src 1720011074.482098424 diff 1040044361
ts2phc[4116.338]: [ts2phc.2.config] ens7f0 master offset 1040044361 s2 freq +900000000

[kni@registry.kni-qe-61 ~]$ oc exec -it ds/linuxptp-daemon  -n openshift-ptp -c linuxptp-daemon-container -- curl -s localhost:9091/metrics | grep clock_state
# HELP openshift_ptp_clock_state 0 = FREERUN, 1 = LOCKED, 2 = HOLDOVER
# TYPE openshift_ptp_clock_state gauge
openshift_ptp_clock_state{iface="eno1239x",node="helix60.lab.eng.rdu2.redhat.com",process="ptp4l"} 0
openshift_ptp_clock_state{iface="ens3f1npx",node="helix60.lab.eng.rdu2.redhat.com",process="ptp4l"} 0
openshift_ptp_clock_state{iface="ens5fx",node="helix60.lab.eng.rdu2.redhat.com",process="dpll"} 1
openshift_ptp_clock_state{iface="ens5fx",node="helix60.lab.eng.rdu2.redhat.com",process="ts2phc"} 1
openshift_ptp_clock_state{iface="ens7fx",node="helix60.lab.eng.rdu2.redhat.com",process="GM"} 0
openshift_ptp_clock_state{iface="ens7fx",node="helix60.lab.eng.rdu2.redhat.com",process="dpll"} 1
openshift_ptp_clock_state{iface="ens7fx",node="helix60.lab.eng.rdu2.redhat.com",process="gnss"} 1
openshift_ptp_clock_state{iface="ens7fx",node="helix60.lab.eng.rdu2.redhat.com",process="ts2phc"} 1

Normal ts2phc offsets and GM clock_state reporting as locked
When ts2phc offsets are high, metrics should show ts2phc clock_state as freerun