-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
4.16
-
None
Description of problem:
After creating boundary clock configurations and boundary ha configuration, pod's log shows that ptp4l cannot be started with no interface specified error.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Create BC1 config 2. Create BC2 config 3. Create BC HA config 4. Delete pod for a good measure 5. Check the pod's linuxptp-daemon-container logs
Actual results:
I0510 12:12:28.365179 3095645 daemon.go:768] ptp4l cmd: /bin/chrt -f 10 /usr/sbin/ptp4l -f /var/run/ptp4l.2.config -m [20/1870]I0510 12:12:28.365661 3095645 daemon.go:698] ptp4l[1715343148]:[ptp4l.2.config] PTP_PROCESS_STATUS:1 no interface specified ... E0510 12:12:28.367660 3095645 daemon.go:856] CmdRun() error waiting for ptp4l: exit status 255
Expected results:
Both ptp4l processes started successfully
Additional info:
Same error for the second ptp4l configuration
- blocks
-
OCPBUGS-35024 PTP Boundary HA configuration cannot handle spaced empty Phc2SysOpts and ptp4lOpts with
- Closed
- is cloned by
-
OCPBUGS-35024 PTP Boundary HA configuration cannot handle spaced empty Phc2SysOpts and ptp4lOpts with
- Closed
- links to
-
RHEA-2024:3718 OpenShift Container Platform 4.17.z bug fix update
- mentioned on
(1 links to, 2 mentioned in, 1 mentioned on)