-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.20
-
None
-
False
-
-
None
-
Important
-
None
-
x86_64
-
QA
-
None
-
None
-
CNF RAN Sprint 283, CNF RAN Sprint 284
-
2
-
Done
-
Release Note Not Required
-
N/A
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-61822. The following is the description of the original issue:
—
Description of problem:
This issue was caught in the PTP OC 2 Port CI. After a configuration change & load the PTP Daemon stops reporting metrics
Version-Release number of selected component (if applicable):
4.20.0-202509111841
How reproducible:
TBD
Steps to Reproduce:
Summary of Polarion test case "validates HTTP PTP events via consumer" of ID 54245
1.Modify the ptp profile ptpClockThresholds
2.Wait for PTP to load the new configuration
3.Modify the same settings again
4.PTP fails to report metrics
Actual results:
PTP no longer reports metrics
Expected results:
PTP reports metrics
Additional info:
- blocks
-
OCPBUGS-70327 4.18 OC 2 Port PTP Cloud Event Proxy skipping reporting PTP processes due to "config does not have profile name"
-
- Closed
-
-
OCPBUGS-74377 PTP OC 2 Port CI: After a configuration change & load the PTP Daemon stops reporting metrics
-
- Closed
-
- clones
-
OCPBUGS-61822 [4.20] PTP OC 2 Port CI: After a configuration change & load the PTP Daemon stops reporting metrics
-
- Closed
-
- is blocked by
-
OCPBUGS-61822 [4.20] PTP OC 2 Port CI: After a configuration change & load the PTP Daemon stops reporting metrics
-
- Closed
-
- is cloned by
-
OCPBUGS-74377 PTP OC 2 Port CI: After a configuration change & load the PTP Daemon stops reporting metrics
-
- Closed
-
- links to