This is a clone of issue OCPBUGS-54693. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-54680. The following is the description of the original issue:
—
Description of problem:
When events are enabled, logs from ptp4l and other commands are sent to the cloud-event-proxy container via a socket. This PR delays the start of the command until after the socket is setup. Otherwise, the early logs are missed, so early state transitions used in metrics are lost
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Start linux-ptp-daemon pod with pull policy set to always so that the cloud-event-proxy container comes up after the linuxptp-daemon-container
2.
3.
Actual results:
The ptp4l process starts early and starting logs are missed by cloud-event-proxy
Expected results:
All logs including starting logs are captured since they are used to generate events
Additional info:
- is blocked by
-
OCPBUGS-54693 Add delay in linuxptp-daemon to wait for socket to be ready
-
- Closed
-
- links to