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

Increasing Clock Class Reporting Frequency

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • 4/17: Ready to merge
    • None
    • None
    • None
    • Done
    • Release Note Not Required
    • N/A
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-53371. The following is the description of the original issue:
      —
      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:

      Steps to Reproduce:

          1.Run ptp and verify clock class with event enabled 
    2.verify localhost9091:metrics  for clock class , should be 6 
    3.kill side car (daemon shoul dbe still running ) 
          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 
    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
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              None
              Bonnie Block Bonnie Block
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: