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

With the introduction of the MCO disruptive test suite in MCO-1652, the tests previously tagged with `Slow` will now run in a periodic (see this comment for more information on tests that previously did not contribute to MCN's component readiness and why). Therefore, it is important that all tests consistently pass.

The `Should properly report MCN conditions on node degrade` test has failed in rehearsal runs, but due to must-gather sanitization, we do not have much visibility into the cause of the failures. Thus, it is quite difficult to understand if the failures are a result of functionality flaws, issues in the test implementation, or interference with other tests. To help understand the true stability of the test, we should improve visibility into the MCN throughout the test runs & use the updates to improve the test's long term stability.

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

4.20 & 4.19

How reproducible:

The failures are seemingly intermittent, but unsure.

Steps to Reproduce:

See the following test runs for example failures:

• https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/64752/rehearse-64752-periodic-ci-openshift-machine-config-operator-release-4.20-periodics-e2e-gcp-mco-disruptive-techpreview/1934760025801101312
• https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/64752/rehearse-64752-periodic-ci-openshift-machine-config-operator-release-4.20-periodics-e2e-metal-ipi-ovn-dualstack-mco-disruptive-techpreview/1934760025994039296

Actual results:

`Should properly report MCN conditions on node degrade` fails.

Expected results:

`Should properly report MCN conditions on node degrade` should consistently pass and failures should better highlight the state of the MCN.

Additional info:

• See this GitHub comment for details on how to run the new MCO suite rehersals.