OPRUN-4518: Remove skip for incompatible operator check after rename of CER

[camilamacedo86]

After we get the PR: openshift/cluster-olm-operator#191 merged we can merge this one.

[openshift-ci-robot]

@camilamacedo86: This pull request references OPRUN-4518 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

After we get the PR: openshift/cluster-olm-operator#191 merged we can merge this one.

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.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: bde414fd-a945-4cd8-9050-f6df82aa932a

📥 Commits

Reviewing files that changed from the base of the PR and between 52410d5 and e2f2c30.

📒 Files selected for processing (1)

• openshift/tests-extension/test/olmv1-incompatible.go

💤 Files with no reviewable changes (1)

• openshift/tests-extension/test/olmv1-incompatible.go

---

Walkthrough

Removed the github.com/openshift/api/features import and eliminated a feature-gate conditional that previously skipped test execution when FeatureGateNewOLMBoxCutterRuntime was enabled, allowing the test to proceed unconditionally.

Changes

Cohort / File(s)	Summary
Feature Gate Removal openshift/tests-extension/test/olmv1-incompatible.go	Deleted import of feature gate package and removed conditional skip logic based on FeatureGateNewOLMBoxCutterRuntime, resulting in direct test flow execution.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[jianzhangbjz]

Hi @Xia-Zhao-rh , could you help verify it? Thanks!
/assign @Xia-Zhao-rh

[tmshort]

/hold
Until #691 merges

[bandrade]

/label qe-approved
/verified by @bandrade

[openshift-ci-robot]

@camilamacedo86: This pull request references OPRUN-4518 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

After we get the PR: openshift/cluster-olm-operator#191 merged we can merge this one.

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-robot]

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

Details

In response to this:

/label qe-approved
/verified by @bandrade

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]

/approved

[camilamacedo86]

/retest-required

[tmshort]

/unhold
#691 merged

[tmshort]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, 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:

• DOWNSTREAM_OWNERS [tmshort]

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

[openshift-ci]

@camilamacedo86: 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.