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

Update KCM node-monitor-grace-period to upstream default value to prevent nodes going "NotReady" for a few seconds

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.15.z
    • 4.14.z, 4.17.0, 4.16.z
    • HyperShift
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, the grace period for a node to become ready was not aligned with upstream behavior. This grace period sometimes caused a node to cycle between `Ready` and `Not ready` states. With this release, the issue is fixed so that the grace period does not cause a node to cycle between the two states. (link:https://issues.redhat.com/browse/OCPBUGS-39077[*OCPBUGS-39077*])
      Show
      * Previously, the grace period for a node to become ready was not aligned with upstream behavior. This grace period sometimes caused a node to cycle between `Ready` and `Not ready` states. With this release, the issue is fixed so that the grace period does not cause a node to cycle between the two states. (link: https://issues.redhat.com/browse/OCPBUGS-39077 [* OCPBUGS-39077 *])
    • Bug Fix
    • Done

      This is a clone of issue OCPBUGS-38259. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-38258. The following is the description of the original issue:
      —
      The issue we're trying to address is that nodes go NotReady for a few seconds. 
      See slack thread https://redhat-external.slack.com/archives/C01C8502FMM/p1717767390381249

              agarcial@redhat.com Alberto Garcia Lamela
              openshift-crt-jira-prow OpenShift Prow Bot
              Jie Zhao Jie Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: