This is a clone of issue OCPBUGS-74237. The following is the description of the original issue:
—
Description of problem:

With the introduction of the fix for OCPBUGS-58023, the update triggered for the `Should properly transition through MCN conditions on rebootless node update` MCN test now completes much quicker. This leads to occasional flakes where we will miss certain conditions passing through the "Unknown" state. As seen in the logs for the test in this run, the update transitions through the `UpdateExecuted` condition so quickly that we miss the "Unknown" state. The test then errors out at a later point because while we continue checking for the "Unknown" state, the update completes and all conditions are flipped back to "False." We should make the test more stable to allow for "Unknown" or "True" conditions to prevent situations where a test has progressed quicker than the poke intervals set in our test.

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

Any version with MCN tests where OCPBUGS-58023 will be backported, so 4.19.z to 4.22.0.

How reproducible:

Intermittent, it depends on the update speed in the cluster.

Steps to Reproduce:

See https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-machine-config-operator-5566-nightly-4.22-e2e-aws-ovn-serial-1of2/2013286948117942272 for an example test run or run the test in a cluster with MCO PR#5527 included.

Actual results:

The `Should properly transition through MCN conditions on rebootless node update` test sometimes flakes.

Expected results:

The `Should properly transition through MCN conditions on rebootless node update` test should always pass.

Additional info:

This test fix should merge in each affected version before the fix for OCPBUGS-58023 to avoid payload test failures.