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

PTP processes revive is taking too long

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • Yes
    • 4/17: Upstream PR is ready , need to pin this to downstream PR in 4.19
    • None
    • None
    • None
    • In Progress
    • Release Note Not Required
    • Hide
      * Previously, log messages from monitored processes, such as `ptp41, `ts2phc`, and so on, were skipped during a container restart operation. With this release, the timing of applying the `ptpconfig` CR for the first time to a node is delayed until at least half of the `ptpconfig` update interval has passed. This delay ensures that the `linuxptp-daemon` and `cloud-event-proxy` containers are initialized and can capture all necessary logs from processes to maintain an accurate history of state transitions. (link:https://issues.redhat.com/browse/OCPBUGS-54967[*OCPBUGS-54967*])
      Show
      * Previously, log messages from monitored processes, such as `ptp41, `ts2phc`, and so on, were skipped during a container restart operation. With this release, the timing of applying the `ptpconfig` CR for the first time to a node is delayed until at least half of the `ptpconfig` update interval has passed. This delay ensures that the `linuxptp-daemon` and `cloud-event-proxy` containers are initialized and can capture all necessary logs from processes to maintain an accurate history of state transitions. (link: https://issues.redhat.com/browse/OCPBUGS-54967 [* OCPBUGS-54967 *])
    • None
    • None
    • None
    • None

      Description of problem:

      The following failures have been rising in our automation

 [FAIL] PTP Recovery ptp process restart [It] should recover the phc2sys process after killing it [ptp-recovery, 49850, test_id:49850] /var/lib/jenkins/workspace/ocp-far-edge-vran-tests/cnf-gotests/test/ran/ptp/tests/ptp_recovery.go:97
[FAIL] PTP Recovery ptp process restart [It] should recover the ts2phc process after the killing a ts2phc process [ptp-recovery, 59863, test_id:59863]

Automation results: 4.16, 4.17, 4.18

      Automation results: 4.16, 4.17, 4.18

      Version-Release number of selected component (if applicable):

          4.16, 4.17, 4.18

      How reproducible:

          kill a PTP service twice in a short instance

      Steps to Reproduce:

      1.Kill PTP related process: oc -n openshift-ptp exec ds/linuxptp-daemon -c linuxptp-daemon-container -- pkill phc2sys                                                                                                            2.Kill the same PTP related process immediately after: oc -n openshift-ptp exec ds/linuxptp-daemon -c linuxptp-daemon-container -- pkill phc2sys

      Actual results:

           The second kill commands exits with an error code of 1; PTP process revives after 2-3 seconds

      Expected results:

          The second kill command exists gracefully with no errors; PTP process revives immediately

      Additional info:

              deliedit@redhat.com David Elie-Dit-Cosaque
              rh-ee-dpopsuev Daniel Popsuevich
              None
              Bonnie Block
              Daniel Popsuevich Daniel Popsuevich
              None
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: