-
Bug
-
Resolution: Done
-
Major
-
None
-
4.18, 4.19, 4.20
-
None
-
Quality / Stability / Reliability
-
False
-
-
1
-
None
-
None
-
None
-
None
-
None
-
OSDOCS Sprint 274, OSDOCS Sprint 275
-
2
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The documentation for https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/machine_configuration/machine-config-index#checking-mc[…]ig-overview is misleading, causing confusion when trying to analyze cluster updates. The documentation should be updated to reflect that ready nodes are calculated as a subset of updated nodes. The code (https://github.com/openshift/machine-config-operator/pull/5/commits/7357cc0318ab2484cc5dd4925956badd340d3bd6#diff-9842793db35f3[…]77fa6d2027080fR106) first identifies all nodes that are fully updated and only then checks which of them are also ready.
Version-Release number of selected component (if applicable):
Affects all recent versions of OpenShift 4.x. Analysis of the controller code and historical PRs shows this behavior has existed since at least 2018.
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Proposed READYMACHINECOUNT Description: Indicates the number of machines that are both running the current machine config and are ready for scheduling. This count will always be less than or equal to updatedMachineCount
Additional info: