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

[4.19] Increasing Clock Class Reporting Frequency

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • 3/25: Upstream PR approved, waiting to merge downstream
    • None
    • None
    • None
    • In Progress
    • Release Note Not Required
    • None
    • None
    • None
    • None
    • None

      Description of problem:

       For Boundary Clock, the GM clock class is read via the PMC command every few seconds and logged only when there is a change in CLOCK CLASS. This causes the sidecar to miss updates on the clock class value if it restarts or fails to read the first event. Increasing the frequency ensures that the latest clock class is always updated.

       

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

          

      How reproducible:

          

       1.Run ptp and verify clock class with event enabled
      2.verify localhost9091:metrics for clock class , should be 6
      3.kill side car
          oc exec ds/linuxptp-daemon -c cloud-event-proxy -n openshift-ptp – sh -c "kill -9 \$(ps aux | grep cloud-event-proxy | grep -v grep | awk '{print \$2}')"
      4. wait for the side car to recover ( daemon should continue to run )
      5. verify the clock class metrics Actual results: should show 6 Expected results: doesn't have clock class metrics

      Additional info:

          

              aputtur@redhat.com Aneesh Puttur
              aputtur@redhat.com Aneesh Puttur
              None
              None
              Bonnie Block Bonnie Block
              None
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: