NO-ISSUE: Remove exception for OCPBUGS-45921

[hongkailiu]

The bug is fixed on both 4.22 and 5.0 [1].

[1]. https://redhat.atlassian.net/browse/OCPBUGS-45921?focusedCommentId=17383073

Summary by CodeRabbit

• Bug Fixes
  • Removed a stale exception for the ingress operator during stable-system availability checks.
  • This keeps operator status handling aligned with the current behavior and avoids showing an outdated special-case message.

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[coderabbitai]

Walkthrough

The stable-system operator transition test no longer accepts the ingress-specific exception mapping.

Changes

Stable-system operator exception change

Layer / File(s)	Summary
Remove ingress exception pkg/monitortests/clusterversionoperator/legacycvomonitortests/operators.go	The testStableSystemOperatorStateTransitions exception callback no longer includes the ingress operator branch.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	PASS: The PR only removes an exception mapping; no Ginkgo It/Describe/Context/When titles were added or changed, and existing JUnit names are static templates.
Test Structure And Quality	✅ Passed	Not applicable: the PR only removes one exception mapping in a helper; no Ginkgo specs, setup/cleanup, waits, or assertions were added or changed.
Microshift Test Compatibility	✅ Passed	No new Ginkgo e2e test was added; this change only removes an exception in monitor-test logic and doesn’t add MicroShift-incompatible coverage.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PASS: The PR only removes an exception in a monitor-test helper; it adds no Ginkgo It/Describe/Context/When blocks or new multi-node assumptions.
Topology-Aware Scheduling Compatibility	✅ Passed	Only a monitor test exception mapping changed; no deployment, controller, or scheduling constraints were introduced.
Ote Binary Stdout Contract	✅ Passed	Changed package has no main/TestMain/suite setup or stdout writes; the modified file is a helper test function only.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	Touched helper adds no Ginkgo tests; no It/Describe/Context/When or IPv4/public-network literals found, so the IPv6/disconnected check isn’t triggered.
No-Weak-Crypto	✅ Passed	The touched test file only removes an operator exception mapping; no weak-crypto APIs, algorithms, or secret comparisons appear in the diff or file.
Container-Privileges	✅ Passed	PASS: The PR only edits pkg/monitortests/.../operators.go test logic; no manifests or privileged/hostNetwork/allowPrivilegeEscalation fields were added or changed.
No-Sensitive-Data-In-Logs	✅ Passed	PR only removes an ingress exception mapping; no new logging or sensitive-data-bearing fields were added in the touched code.
Title check	✅ Passed	The title clearly matches the change: removing the exception for OCPBUGS-45921.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[hongkailiu]

/cc @candita

[openshift-merge-bot]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

[candita]

Looks like an install failure, so retesting:
/test e2e-gcp-csi

[candita]

/assign

[candita]

/lgtm

[hongkailiu]

/verified @hongkailiu

Sippy stats gave us a level of confidence. ^_^

[openshift-ci-robot]

@hongkailiu: The /verified command must be used with one of the following actions: by, later, remove, or bypass. See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

Details

In response to this:

/verified @hongkailiu

Sippy stats gave us a level of confidence. ^_^

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[hongkailiu]

/retest-required

[hongkailiu]

/verified by @hongkailiu

[openshift-ci-robot]

@hongkailiu: This PR has been marked as verified by @hongkailiu.

Details

In response to this:

/verified by @hongkailiu

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[tmshort]

Not sure I can... but...
/approve

[sosiouxme]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: candita, hongkailiu, sosiouxme, tmshort

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [sosiouxme]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hongkailiu]

/jira refresh

[openshift-ci-robot]

@hongkailiu: This pull request explicitly references no jira issue.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@hongkailiu: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.