-
Bug
-
Resolution: Unresolved
-
Normal
-
4.18, 4.19, 4.20, 4.21
-
None
-
None
-
False
-
-
None
-
Critical
-
None
-
x86_64
-
QA
-
2026-Feb-16: Discussed about how to fix the general case of this. Its causing QE problems with CI.
-
None
-
None
-
CNF RAN Sprint 280, CNF RAN Sprint 281, CNF RAN Sprint 282, CNF RAN Sprint 283, CNF RAN Sprint 284
-
5
-
In Progress
-
Known Issue
-
When switching between PTP profiles, metrics from the previously applied profile might not be cleaned up correctly. This issue is most noticeable when changing network interfaces (NICs). As a workaround, you can restart the pod to clean up the metrics.
-
None
-
None
-
None
-
None
Description of problem:
4.21 PTP Cloud Event Proxy reports stale metrics about processes which are associated with an unused NIC
Version-Release number of selected component (if applicable):
4.21.0-202512011821
How reproducible:
100%
Steps to Reproduce:
1.Apply PTP Configuration which uses multiple NICs. T-BC Dual Card, ifaces ens1fx & ens2fx in context. 2.Apply new Apply PTP Configuration which uses single NIC. T-BC Single Card, iface ens2fx in context. 3.CEP will report metrics for an unused interface. ens1fx in context.
Actual results:
# 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="helix65.lab.eng.rdu2.redhat.com",process="phc2sys"} 1
openshift_ptp_clock_state{iface="ens1fx",node="helix65.lab.eng.rdu2.redhat.com",process="dpll"} 1
openshift_ptp_clock_state{iface="ens1fx",node="helix65.lab.eng.rdu2.redhat.com",process="ts2phc"} 0
openshift_ptp_clock_state{iface="ens2fx",node="helix65.lab.eng.rdu2.redhat.com",process="T-BC"} 1
openshift_ptp_clock_state{iface="ens2fx",node="helix65.lab.eng.rdu2.redhat.com",process="dpll"} 1
openshift_ptp_clock_state{iface="ens2fx",node="helix65.lab.eng.rdu2.redhat.com",process="ptp4l"} 1
openshift_ptp_clock_state{iface="ens2fx",node="helix65.lab.eng.rdu2.redhat.com",process="ts2phc"} 1
Expected results:
# 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="helix65.lab.eng.rdu2.redhat.com",process="phc2sys"} 1
openshift_ptp_clock_state{iface="ens2fx",node="helix65.lab.eng.rdu2.redhat.com",process="T-BC"} 1
openshift_ptp_clock_state{iface="ens2fx",node="helix65.lab.eng.rdu2.redhat.com",process="dpll"} 1
openshift_ptp_clock_state{iface="ens2fx",node="helix65.lab.eng.rdu2.redhat.com",process="ptp4l"} 1
openshift_ptp_clock_state{iface="ens2fx",node="helix65.lab.eng.rdu2.redhat.com",process="ts2phc"} 1
Additional info:
- is duplicated by
-
OCPBUGS-74884 GNR-D stale metrics reporting after changing ptpconfig
-
- Closed
-