-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
4.14.z, 4.18.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
3/25: Upstream Approved. Fix will be downstream to 4.19 and backported
-
None
-
None
-
None
-
Done
-
Release Note Not Required
-
N/A
-
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:
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:
- blocks
-
OCPBUGS-54960 Increasing Clock Class Reporting Frequency
-
- Closed
-
- is blocked by
-
OCPBUGS-53452 [4.19] Increasing Clock Class Reporting Frequency
-
- Closed
-
- is cloned by
-
OCPBUGS-53452 [4.19] Increasing Clock Class Reporting Frequency
-
- Closed
-
-
OCPBUGS-54960 Increasing Clock Class Reporting Frequency
-
- Closed
-
- links to
-
RHBA-2025:3577 OpenShift Container Platform 4.18.z bug fix update
(1 links to)