Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-63158

T-TSC/T-BC Holdover: With TR / T-TSC configuration only ts2phc metrics reports unlocked, ptp4l metric is reported

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • x86_64
    • QA
    • 2025-11-03 PR in review
    • None
    • CNF RAN Sprint 278, CNF RAN Sprint 280
    • 2
    • Done
    • Known Issue
    • Hide
      * Using a Telecom Time Synchronous Clock (T-TSC) configuration causes the ts2phc metrics to report "unlocked" instead of "locked". As a result, you might encounter inaccurate Precision Time Protocol (PTP) clock state reporting. To work around this issue, remove the `ts2phc` metric. OCPBUGS-63158
      Show
      * Using a Telecom Time Synchronous Clock (T-TSC) configuration causes the ts2phc metrics to report "unlocked" instead of "locked". As a result, you might encounter inaccurate Precision Time Protocol (PTP) clock state reporting. To work around this issue, remove the `ts2phc` metric. OCPBUGS-63158
    • None
    • None
    • None
    • None

      Description of problem:

      With TR / T-TSC configuration only ts2phc metrics reports unlocked, ptp4l metric is reported.

      Version-Release number of selected component (if applicable):

          ptp-operator.v4.20.0-202510141524

      How reproducible:

      100%    

      Steps to Reproduce:

          1.Deploy PTP with T-TSC / TR configuration
      

      Actual results:

          # TYPE openshift_ptp_clock_state gauge
      openshift_ptp_clock_state{iface="CLOCK_REALTIME",node="helix65.lab.eng.rdu2.redhat.com",process="phc2sys"} 1
      openshift_ptp_clock_state{iface="ens1fx",node="helix65.lab.eng.rdu2.redhat.com",process="dpll"} 1
      openshift_ptp_clock_state{iface="ens1fx",node="helix65.lab.eng.rdu2.redhat.com",process="ts2phc"} 1
      openshift_ptp_clock_state{iface="ens2fx",node="helix65.lab.eng.rdu2.redhat.com",process="T-BC"} 1
      openshift_ptp_clock_state{iface="ens2fx",node="helix65.lab.eng.rdu2.redhat.com",process="dpll"} 1
      openshift_ptp_clock_state{iface="ens2fx",node="helix65.lab.eng.rdu2.redhat.com",process="ptp4l"} 1
      openshift_ptp_clock_state{iface="ens2fx",node="helix65.lab.eng.rdu2.redhat.com",process="ts2phc"} 0

      Expected results:

          TBD; removal of ts2phc metric and ptp4l?

      Additional info:

      With T-BC / TR & TT Configuration    
      # HELP openshift_ptp_clock_state 0 = FREERUN, 1 = LOCKED, 2 = HOLDOVER
      # TYPE openshift_ptp_clock_state gauge
      openshift_ptp_clock_state{iface="CLOCK_REALTIME",node="helix65.lab.eng.rdu2.redhat.com",process="phc2sys"} 1
      openshift_ptp_clock_state{iface="ens1fx",node="helix65.lab.eng.rdu2.redhat.com",process="dpll"} 1
      openshift_ptp_clock_state{iface="ens1fx",node="helix65.lab.eng.rdu2.redhat.com",process="ts2phc"} 1
      openshift_ptp_clock_state{iface="ens2fx",node="helix65.lab.eng.rdu2.redhat.com",process="T-BC"} 1
      openshift_ptp_clock_state{iface="ens2fx",node="helix65.lab.eng.rdu2.redhat.com",process="dpll"} 1
      openshift_ptp_clock_state{iface="ens2fx",node="helix65.lab.eng.rdu2.redhat.com",process="ts2phc"} 1

              vgrinber@redhat.com Vitaly Grinberg
              rh-ee-dpopsuev Daniel Popsuevich
              None
              None
              Daniel Popsuevich Daniel Popsuevich
              Katie Drake Katie Drake
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: