Loading...

XML

Word

Printable

Severity:
Moderate
Regression:
None
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Release Note Text:

Hide
* Previously, the grace period for a node to become ready was not aligned with upstream, and in some situations, the previous set period made the node cycle between `Ready` and `Not ready`. (link:https://issues.redhat.com/browse/OCPBUGS-38258[*OCPBUGS-38258*])

Show
* Previously, the grace period for a node to become ready was not aligned with upstream, and in some situations, the previous set period made the node cycle between `Ready` and `Not ready`. (link: https://issues.redhat.com/browse/OCPBUGS-38258 [*OCPBUGS-38258*])
Release Note Type:
Bug Fix
Release Note Status:
Done
Target Version:

4.16.z
Target Backport Versions:

4.14.z, 4.15.z, 4.16.z

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

blocks

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

is cloned by

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

links to

RHBA-2024:6004 OpenShift Container Platform 4.16.z bug fix update