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

The blocking `e2e-aws-ovn-techpreview-serial` suite started failing on the PIS tests on 4/28. The failures were fixed by reverting MCO PR #5003 in MCO PR #5013. More information can be found in the comments on TRT-2095. However, the underlying issue the test failure highlights should still be investigated, as customers may encounter the same edge case.

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

4.19 - Specifically versions including the changes from MCO PR #5003

How reproducible:

Always in clusters with MCO PR #5003.

Steps to Reproduce:

1. Launch a cluster with the problematic code included. The following can be used in Clusterbot.

launch 4.19.0-0.ci-2025-04-28-053740 aws,techpreview

2. Apply a PIS & track the logs.

3. See that the MCN does not reflect the PIS applied.

Actual results:

PIS tests are failing in the `e2e-aws-ovn-techpreview-serial` test suite.

Expected results:

PIS tests should be stable in the blocking test suite.

Additional info:

• See the following rehearsal job for failures:
  • https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial/1916808388444950528
  • https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial/1916729021006090240
• Launching a cluster against with the original PR included in the payload (launch 4.19.0-0.ci-2025-04-28-053740 aws,techpreview) results in failing origin tests
• Launching a cluster against the revert PR (launch 4.19.0-0.ci-2025-04-28-053740 aws,techpreview) results in passing origin tests
• See this Slack thread for more information