The OLMv0 networkpolicy test is failing on multi-arch and arm64 variants because the catalog-operator NetworkPolicy egress rule 0 no longer has the expected port specification.

All failures show the same error at networkpolicy.go:155:
catalog-operator: rule 0 egress ports count
Expected <int>: 0
to equal <int>: 1

Affected Tests

• Test: [sig-operator][Jira:OLM] OLMv0 networkpolicy PolarionID:83105-[OTP][Skipped:Disconnected]olmv0 static networkpolicy on ocp
• Test ID: openshift-tests:af6a09607b23a126f1412f71e2740a46
• Regression IDs: 36088 (Architecture:multi), 36089 (Architecture:arm64)
• Release: 4.22

Version-Release number
4.22

How reproducible
Always (100% failure consistency across all 3 analyzed job runs)

Steps to Reproduce
1. Run the multi-arch nightly CI job periodic-ci-openshift-multiarch-main-nightly-4.22-ocp-e2e-aws-ovn-multi-x-x
2. The OLMv0 networkpolicy test verifies the catalog-operator NetworkPolicy egress rules
3. The test fails because rule 0's ports array is empty when it expects 1 port

Actual results
The test fails with:
catalog-operator: rule 0 egress ports count
Expected <int>: 0
to equal <int>: 1

Pass rate dropped from 100% to 85.71%.
Pass sequence: FFFSSSSSSSS (3 consecutive recent failures starting Mar 2, 8 older successes).

Expected results
The catalog-operator NetworkPolicy egress rule 0 should have a ports specification with 1 port, or the test should be updated to match the new structure.

Root Cause
The catalog-operator's NetworkPolicy egress rule structure changed around February 12, 2026. The test file at /build/tests-extension/test/qe/util/olmv0util/networkpolicy.go:155 expects rule 0 to have a
ports array with 1 entry, but it's now empty.

Failure Details

• Job: periodic-ci-openshift-multiarch-main-nightly-4.22-ocp-e2e-aws-ovn-multi-x-x
• First failing run: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-multiarch-main-nightly-4.22-ocp-e2e-aws-ovn-multi-x-x/2021977075845435392
• Payload: 4.22.0-0.nightly-multi-2026-02-12-105448
• Regression opened: 2026-03-03
• Affected variants: Architecture:multi and Architecture:arm64, Platform:aws, Network:ovn, Topology:ha, Upgrade:none

Sippy Test Details

• Regression 36088 (multi): https://sippy-auth.dptools.openshift.org/sippy-ng/component_readiness/test_details?Architecture=multi&FeatureSet=default&Installer=ipi&LayeredProduct=none&Network=ovn&Platform=aws&Suite=unknown&Topology=ha&Upgrade=none&baseEndTime=2026-02-03T23%3A59%3A59Z&baseRelease=4.21&baseStartTime=2026-01-04T00%3A00%3A00Z&capability=Other&columnGroupBy=Network%2CPlatform%2CTopology&component=OLM&confidence=95&dbGroupBy=Architecture%2CFeatureSet%2CInstaller%2CLayeredProduct%2CNetwork%2CPlatform%2CSuite%2CTopology%2CUpgrade&environment=Architecture%3Amulti+FeatureSet%3Adefault+Installer%3Aipi+LayeredProduct%3Anone+Network%3Aovn+Platform%3Aaws+Suite%3Aunknown+Topology%3Aha+Upgrade%3Anone&sampleEndTime=2026-03-03T20%3A00%3A00Z&sampleRelease=4.22&sampleStartTime=2026-02-24T00%3A00%3A00Z&testId=openshift-tests%3Aaf6a09607b23a126f1412f71e2740a46
• Regression 36089 (arm64): https://sippy-auth.dptools.openshift.org/sippy-ng/component_readiness/test_details?Architecture=arm64&FeatureSet=default&Installer=ipi&LayeredProduct=none&Network=ovn&Platform=aws&Suite=unknown&Topology=ha&Upgrade=none&baseEndTime=2026-02-03T23%3A59%3A59Z&baseRelease=4.21&baseStartTime=2026-01-04T00%3A00%3A00Z&capability=Other&columnGroupBy=Network%2CPlatform%2CTopology&component=OLM&confidence=95&dbGroupBy=Architecture%2CFeatureSet%2CInstaller%2CLayeredProduct%2CNetwork%2CPlatform%2CSuite%2CTopology%2CUpgrade&environment=Architecture%3Aarm64+FeatureSet%3Adefault+Installer%3Aipi+LayeredProduct%3Anone+Network%3Aovn+Platform%3Aaws+Suite%3Aunknown+Topology%3Aha+Upgrade%3Anone&sampleEndTime=2026-03-03T20%3A00%3A00Z&sampleRelease=4.22&sampleStartTime=2026-02-24T00%3A00%3A00Z&testId=openshift-tests%3Aaf6a09607b23a126f1412f71e2740a46

Filed by: jgeorge@redhat.com