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

With WPC card configured as GM or BC, phc2sys clock lock state is shown as FREERUN in ptp metrics while it should be LOCKED

XMLWordPrintable

    • Important
    • No
    • Proposed
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      When phc2sysOpts is configured in the GM ptp profile, ptp metrics show phc2sys as FREERUN. 

It is likely due to GM config does not have slave interface as per Aneesh.

# 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="helix48.ptp.lab.eng.bos.redhat.com",process="phc2sys"} 0
openshift_ptp_clock_state{iface="ens5fx",node="helix48.ptp.lab.eng.bos.redhat.com",process="ptp4l"} 1
openshift_ptp_clock_state{iface="ens7fx",node="helix48.ptp.lab.eng.bos.redhat.com",process="ts2phc"} 1

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

      4.13

      How reproducible:

      100%

      Steps to Reproduce:

      1. Configure GM on a cluster with phc2sysOpts
2. check ptp metrics
3.

      Actual results:

      openshift_ptp_clock_state for phc2sys is in FREERUN

      Expected results:

      openshift_ptp_clock_state should be in LOCKED state

      Additional info:

       

              aputtur@redhat.com Aneesh Puttur
              rhn-support-yliu1 Yang Liu
              Ofer Bochan Ofer Bochan
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: