Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-54693

Add delay in linuxptp-daemon to wait for socket to be ready

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • Done
    • Release Note Not Required
    • N/A
    • None
    • None
    • None
    • None

      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:

              deliedit@redhat.com David Elie-Dit-Cosaque
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              None
              Bonnie Block Bonnie Block
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: