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

T-BC Holdover: Clock Class is unable to upgrade back to Locked (6) after degrading

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Critical
    • None
    • Hide
      9/11: Build available for test, QE on track to verify
      08/28: Merged downstream, ready for QE to verify
      Show
      9/11: Build available for test, QE on track to verify 08/28: Merged downstream, ready for QE to verify
    • None
    • None
    • CNF RAN Sprint 275, CNF RAN Sprint 276
    • 2
    • In Progress
    • Release Note Not Required
    • None
    • None
    • None
    • None
    • None

      Description of problem:

          The clock class doesn't return to Locked (6) from a degraded clock class (135, 165, 248).

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

          ptp-operator.v4.20.0-202508140915

      How reproducible:

          100%

      Steps to Reproduce:

          1.Cause a loss of upstream clock by taking down the upstream interface connection; ip link set ens2f3 down.
          2.Clock Class downgrades.
          3.Recover upstream interface; ip link set ens2f3 up.     

      Actual results:

         Clock Class remains on the last class; e.g. Clock Class degraded to 135, upstream clock connection resumes, Clock Class remains on 135.

      Expected results:

          Clock Class returns to locked class; e.g. Clock Class degraded to 135, upstream clock connection resumes, Clock Class turns back to 6.

      Additional info:

          

              vgrinber@redhat.com Vitaly Grinberg
              rh-ee-dpopsuev Daniel Popsuevich
              None
              None
              Daniel Popsuevich Daniel Popsuevich
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: