-
Bug
-
Resolution: Duplicate
-
Normal
-
None
-
4.18.z
-
None
-
None
-
False
-
-
None
-
Important
-
None
-
x86_64
-
QA
-
2026-Jan-19: Dev not had time to look into yet
-
None
-
None
-
CNF RAN Sprint 283, CNF RAN Sprint 284
-
2
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
PTP Cloud Event Proxy has issues with consuming process logs during the parsing of the configuration name
Version-Release number of selected component (if applicable):
4.18.0-202512111312
How reproducible:
TBD
Steps to Reproduce:
1. Deploy PTP with Cloud Event Proxy
2. Perform actions which will cause the PTP Pod / Cloud Event Proxy pod to restart such as configuration changes or killing.
3. Follow Cloud Event Proxy logs for "...Skipping..." messages
Actual results:
time="2026-01-04T22:41:31Z" level=info msg="phc2sys config does not have profile name, time="2026-01-04T22:41:31Z" level=info msg="ptp4l config does not have profile name, skipping. "
Expected results:
Additional info:
- duplicates
-
OCPBUGS-74377 PTP OC 2 Port CI: After a configuration change & load the PTP Daemon stops reporting metrics
-
- Closed
-
- is blocked by
-
OCPBUGS-74296 PTP OC 2 Port CI: After a configuration change & load the PTP Daemon stops reporting metrics
-
- Closed
-