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

Make ptpClockThreshold configurable [4.14]

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • 4.14.z, 4.15.z, 4.17.z, 4.16.z, 4.18.z, 4.19
    • GitOps ZTP
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Telco kube-compare Sprint 267, Telco kube-compare Sprint 268
    • 2
    • In Progress
    • Release Note Not Required
    • None
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-52492. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-51010. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-49900. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-49786. The following is the description of the original issue:
      —
      Description of problem:

      We are missing ptpClockThreshold which is configurable for all configs

ptpClockThreshold:
     holdOverTimeout: 5  
     maxOffsetThreshold: 100
     minOffsetThreshold: -100

These defaults are great, but the cluster-compare template should allow them to be set to other values without invalidating the RDS or showing up as cluster-compare differences.

We should only provide examples in source-crs for the *ForEvent variants.

              jramsay1@redhat.com Jim Ramsay
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              None
              Dwaine Gonyier Dwaine Gonyier
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: