Description of problem:

This is a bug to track and allow a backport for the work completed by team MCO in TRT-2106.

Version-Release number of selected component (if applicable):

First seen in 4.20, now being seen in 4.19 as well.

How reproducible:

Intermittent flakiness,

Steps to Reproduce:

• See an example 4.19 failure here: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.19-e2e-gcp-ovn-techpreview-serial/1925914196894027776
• See an example 4.20 failure here: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview-serial/1920187644701052928

Actual results:

Sometimes the `Should have MCN properties matching associated node properties for nodes in custom MCPs` test will timeout on the custom MCP cleanup process with the following issue.

    [FAILED] Timed out after 300.003s.
    Timed out waiting for MCP 'worker' to be in 'Updated' state with 2 ready machines.
    Expected
        <bool>: false
    to be true
    In [It] at: github.com/openshift/origin/test/extended/machine_config/helpers.go:541 @ 05/07/25 23:04:33.133

Expected results:

Cleanup should always complete successfully.

Additional info:

See Slack conversation here: https://redhat-internal.slack.com/archives/C01CQA76KMX/p1746798170524479?thread_ts=1745580815.870399&cid=C01CQA76KMX