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

PTP OC 2 Port CI: After a configuration change & load the PTP Daemon stops reporting metrics

XMLWordPrintable

    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • x86_64
    • QA
    • None
    • None
    • CNF RAN Sprint 283, CNF RAN Sprint 284
    • 2
    • In Progress
    • Bug Fix
    • Hide
      Before this update, a race condition existed where the `linuxptp-daemon` monitoring logic required Precision Time Protocol (PTP) profiles to be fully loaded before it would allow metric gathering to proceed. This meant that if the container restarted and the collection cycle began before those profiles were ready, the `process_status metric` was not collected, resulting in significant gaps in telemetry and unreliable health reporting after initialization. With this release, the `process_status collection` has been decoupled from the `profile-loading` state, ensuring the metric is gathered even if the profiles are not yet loaded. (link:https://issues.redhat.com/browse/OCPBUGS-74377[OCPBUGS-74377])
      Show
      Before this update, a race condition existed where the `linuxptp-daemon` monitoring logic required Precision Time Protocol (PTP) profiles to be fully loaded before it would allow metric gathering to proceed. This meant that if the container restarted and the collection cycle began before those profiles were ready, the `process_status metric` was not collected, resulting in significant gaps in telemetry and unreliable health reporting after initialization. With this release, the `process_status collection` has been decoupled from the `profile-loading` state, ensuring the metric is gathered even if the profiles are not yet loaded. (link: https://issues.redhat.com/browse/OCPBUGS-74377 [ OCPBUGS-74377 ])
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-74296. The following is the description of the original issue:
      —
      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:

              jacding@redhat.com Jack Ding
              rh-ee-dpopsuev Daniel Popsuevich
              Daniel Popsuevich
              None
              Daniel Popsuevich Daniel Popsuevich
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: