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

During a soak test linuxptp-daemon-container reports 'clock jumped forward or running faster than expected!' error message

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • No
    • Hide
      9/28: chronyd was running , reporter will disable NTP and use other recommendation and to verify again; the master node doesn't have valid time source. Need to update test master node
      9/19: Task assigned
      Show
      9/28: chronyd was running , reporter will disable NTP and use other recommendation and to verify again; the master node doesn't have valid time source. Need to update test master node 9/19: Task assigned
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      During a soak test I am seeing one `clockcheck: clock jumped forward or running faster than expected!` message in the logs after ~60hours of running. This seems to be sporadic and it only showed up on one environment so far.

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

      4.14.0-rc.0
ptp-operator.v4.14.0-202308240205

      How reproducible:

      Not clear, so far reproduces on a single test environment after ~60 hours

      Steps to Reproduce:

      1. Leave SNO with Telco DU profile running for a 72h soak tests
2. Check linuxptp-daemon-container container logs for jump errors

      Actual results:

      One `clockcheck: clock jumped forward or running faster than expected!` occurence

      Expected results:

      No clock jump errors reported

      Additional info:

      The issue shows on a ZTSYSTEMS Proteus with Intel E810-XXV-4 NIC fw 4.22

Attaching must-gather and sosreport.

              josricha@redhat.com Joseph Richard
              mcornea@redhat.com Marius Cornea
              None
              None
              Gowrishankar Rajaiyan Gowrishankar Rajaiyan
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: