1. Proposed title of this feature request

Ensure Accurate UPDATED Status in oc get machineconfignodes Output During MCP Rollout

2. What is the nature and description of the request?

Currently, when rolling out updates via the MachineConfigPool (MCP), the oc get machineconfignodes output that can show inconsistent statuses for worker nodes. Specifically:

Nodes with differing DesiredConfig and CurrentConfig should be in an UPDATING state.

Nodes that have not yet transitioned to the new DesiredConfig should not be marked as UPDATED=True.

The expected behavior is that a node should only be marked as UPDATED=True when its CurrentConfig matches the DesiredConfig. Any node still referencing the old render should not be considered updated.

This request is to enhance the status reporting mechanism to correctly reflect the MCP rollout progress.

3. Why does the customer need this? (List the business requirements here)

Improved Visibility: Incorrect statuses lead to confusion when determining the actual rollout state.

Better Debugging & Troubleshooting: Misleading UPDATED=True statuses can cause administrators to overlook nodes that haven't actually applied the latest MachineConfig.

Operational Efficiency: Accurate reporting ensures that automation and monitoring tools do not falsely assume a completed update, preventing potential deployment issues.

4. List any affected packages or components.

Machine Config Operator