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

Update MaxInSpecOffset to 1500 for T-GM for all configs

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 4.14.z, 4.15.z, 4.17.z, 4.16.z, 4.18.z, 4.19
    • GitOps ZTP
    • None
    • Telco kube-compare Sprint 266
    • 1
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      T-GM uses the MaxInSpecOffset value to determine the state change from HOLDOVER to FREERUN. By default, HoldoverTimeout is set to 14,400 seconds, LocalMaxHoldoverOffset is 1,500 ns, and MaxInSpecOffset is set to 100 ns. With this configuration, the holdover state times out in 16 minutes due to the slope increment occurring every second, reaching MaxInSpecOffset of 100ns within 16 minutes.E810 support 4 hours of holdover and to keep this behavior consistent need to set default MaxInSpecOffset to 1500
       
      These values should be configurable by end-users and allowed to be different in the cluster-compare templates, but default to the values below:
       

      Actual results:

           LocalMaxHoldoverOffSet: 1500 LocalHoldoverTimeout: 14400 MaxInSpecOffset: 100 

      Expected results:

           LocalMaxHoldoverOffSet: 1500 LocalHoldoverTimeout: 14400 MaxInSpecOffset: 1500 

      Additional info:

          

              jramsay1@redhat.com Jim Ramsay
              aputtur@redhat.com Aneesh Puttur
              Hen Shay Hassid Hen Shay Hassid
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: