Description of problem: phc2sys reports offset for master ports and the PTP events generate events for those offsets. phc2sys[859300.541]: [ptp4l.0.config] ens3f1 rms 52 max 52 freq -3081 +/- 0 delay 2542 +/- 0 Since the offsets for master ports are not clearly understood, the events generated for that ports are not valid . Actual results: Generates offset events and metrics for master ports Expected results: Do not show offset metrics and events for master ports Additional info:
issue is verified in: [obochan@obochan ~]$ oc version Client Version: 4.8.0 Server Version: 4.11.0-0.nightly-2022-05-25-193227 Kubernetes Version: v1.23.3+ad897c4 [obochan@obochan ~]$ oc exec -it linuxptp-daemon-tqbbh -n openshift-ptp cloud-event-proxy -- curl 127.0.0.1:9091/metrics | grep openshift_ptp_clock_state Defaulted container "cloud-event-proxy" out of: cloud-event-proxy, kube-rbac-proxy, linuxptp-daemon-container # 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="cnfde4.ptp.lab.eng.bos.redhat.com",process="phc2sys"} 1 openshift_ptp_clock_state{iface="ens1fx",node="cnfde4.ptp.lab.eng.bos.redhat.com",process="ptp4l"} 1 openshift_ptp_clock_state{iface="ens4fx",node="cnfde4.ptp.lab.eng.bos.redhat.com",process="ptp4l"} 1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.11.0 extras and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5070