Description of problem:

MCN tests are failing in the `e2e-metal-ovn-two-node-fencing` and `e2e-metal-ovn-two-node-arbiter` test suites. Since these tests are impacting the component readiness score of MCN in Sippy, it is important to understand the root cause of these failures and remediate as possible.

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

4.19

How reproducible:

Unknown, but from initial judgement of the test errors, always.

Steps to Reproduce:

See here for rehearsal job with failures.

Actual results:

`Should have MCN properties matching associated node properties for nodes in default MCPs` MCN test is not stable on two-node Openshift.

Expected results:

MCN tests should be stable in all tests impacting component readiness score.

Additional info:

See this Slack thread for more information on the issue and impact.