[release-4.20] OCPBUGS-99312: Disable Knative e2e Cypress tests in CI

[cajieh]

Manual backport from PR.

Analysis / Root cause:
The Knative Cypress suite (features/e2e/knative-ci.feature) is failing intermittently in CI with a perspective-switcher-menu-option timeout during the knative beforeEach hook (cy.initAdmin() → perspective switcher). This has driven a high failure rate on e2e-aws-console (including release-4.22), blocking unrelated PRs such as console-operator changes. The flake is timing-related (PatternFly menu portal + React 18 concurrent rendering), not a product regression in Knative UI.

Solution description:
Temporarily disable Knative Cypress execution in CI orchestration so other PRs can merge while the flake is fixed

Test cases:

• CI: confirm Knative Cypress is not run in headless/nightly aggregation paths.
• CI: confirm non-Knative Cypress suites still run as before.
• Follow-up: re-enable Knative tests after OCPBUGS-99226 fix lands and knative/e2e-aws-console is stable.

Browser conformance:

• Chrome
• Firefox
• Safari (or Epiphany on Linux)

Additional info:

Reviewers and assignees:

Summary by CodeRabbit

• Tests
  • Disabled Knative Cypress and end-to-end test scenarios in nightly, headless, and CI test runs.
  • Other test suites and artifact/report generation remain unchanged.

[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: LGTM mode

[openshift-ci-robot]

@cajieh: This pull request references Jira Issue OCPBUGS-99312, which is invalid:

• expected the bug to target either version "4.20." or "openshift-4.20.", but it targets "5.0.0" instead
• expected Jira Issue OCPBUGS-99312 to depend on a bug targeting a version in 4.21.0, 4.21.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Manual backport from PR.

Analysis / Root cause:
The Knative Cypress suite (features/e2e/knative-ci.feature) is failing intermittently in CI with a perspective-switcher-menu-option timeout during the knative beforeEach hook (cy.initAdmin() → perspective switcher). This has driven a high failure rate on e2e-aws-console (including release-4.22), blocking unrelated PRs such as console-operator changes. The flake is timing-related (PatternFly menu portal + React 18 concurrent rendering), not a product regression in Knative UI.

Solution description:
Temporarily disable Knative Cypress execution in CI orchestration so other PRs can merge while the flake is fixed

Test cases:

• CI: confirm Knative Cypress is not run in headless/nightly aggregation paths.
• CI: confirm non-Knative Cypress suites still run as before.
• Follow-up: re-enable Knative tests after OCPBUGS-99226 fix lands and knative/e2e-aws-console is stable.

Browser conformance:

• Chrome
• Firefox
• Safari (or Epiphany on Linux)

Additional info:

Reviewers and assignees:

Summary by CodeRabbit

• Tests
• Disabled Knative Cypress and end-to-end test scenarios in nightly, headless, and CI test runs.
• Other test suites and artifact/report generation remain unchanged.

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]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: fac26bd5-ee52-4851-87e1-3507317be9a0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[cajieh]

/jira refresh

[openshift-ci-robot]

@cajieh: This pull request references Jira Issue OCPBUGS-99312, which is invalid:

• expected the bug to target either version "4.20." or "openshift-4.20.", but it targets "4.22.0" instead
• expected Jira Issue OCPBUGS-99312 to depend on a bug targeting a version in 4.21.0, 4.21.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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.

[cajieh]

/jira refresh

[openshift-ci-robot]

@cajieh: This pull request references Jira Issue OCPBUGS-99312, which is invalid:

• expected Jira Issue OCPBUGS-99312 to depend on a bug targeting a version in 4.21.0, 4.21.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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.

[cajieh]

/label backport-risk-assessed

[cajieh]

/jira refresh

[openshift-ci-robot]

@cajieh: This pull request references Jira Issue OCPBUGS-99312, which is invalid:

• expected Jira Issue OCPBUGS-99312 to depend on a bug targeting a version in 4.21.0, 4.21.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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.

[cajieh]

/jira refresh

[openshift-ci-robot]

@cajieh: This pull request references Jira Issue OCPBUGS-99312, which is invalid:

• expected the bug to target only the "4.20.z" version, but multiple target versions were set
• expected Jira Issue OCPBUGS-99312 to depend on a bug targeting a version in 4.21.0, 4.21.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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.

[cajieh]

/jira refresh

[openshift-ci-robot]

@cajieh: This pull request references Jira Issue OCPBUGS-99312, which is invalid:

• expected Jira Issue OCPBUGS-99312 to depend on a bug targeting a version in 4.21.0, 4.21.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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.

[cajieh]

/jira refresh

[openshift-ci-robot]

@cajieh: This pull request references Jira Issue OCPBUGS-99312, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.20.z) matches configured target version for branch (4.20.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-99311 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-99311 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0, 4.21.z
• bug has dependents

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.

[cajieh]

/lgtm
/approve
/verified by CI

[openshift-ci]

@cajieh: you cannot LGTM your own PR.

Details

In response to this:

/lgtm
/approve
/verified by CI

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.

[openshift-ci-robot]

@cajieh: This PR has been marked as verified by CI.

Details

In response to this:

/lgtm
/approve
/verified by CI

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.

[rhamilto]

/approve
/lgtm

[openshift-merge-bot]

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-gcp-console

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cajieh, rhamilto

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 [rhamilto]

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

[cajieh]

/retest

[openshift-ci]

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

[openshift-ci-robot]

@cajieh: Jira Issue Verification Checks: Jira Issue OCPBUGS-99312
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-99312 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Manual backport from PR.

Analysis / Root cause:
The Knative Cypress suite (features/e2e/knative-ci.feature) is failing intermittently in CI with a perspective-switcher-menu-option timeout during the knative beforeEach hook (cy.initAdmin() → perspective switcher). This has driven a high failure rate on e2e-aws-console (including release-4.22), blocking unrelated PRs such as console-operator changes. The flake is timing-related (PatternFly menu portal + React 18 concurrent rendering), not a product regression in Knative UI.

Solution description:
Temporarily disable Knative Cypress execution in CI orchestration so other PRs can merge while the flake is fixed

Test cases:

• CI: confirm Knative Cypress is not run in headless/nightly aggregation paths.
• CI: confirm non-Knative Cypress suites still run as before.
• Follow-up: re-enable Knative tests after OCPBUGS-99226 fix lands and knative/e2e-aws-console is stable.

Browser conformance:

• Chrome
• Firefox
• Safari (or Epiphany on Linux)

Additional info:

Reviewers and assignees:

Summary by CodeRabbit

• Tests
• Disabled Knative Cypress and end-to-end test scenarios in nightly, headless, and CI test runs.
• Other test suites and artifact/report generation remain unchanged.

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.

[cajieh]

/cherry-pick release-4.19

[openshift-cherrypick-robot]

@cajieh: new pull request created: #16802

Details

In response to this:

/cherry-pick release-4.19

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.

[cajieh]

/cherry-pick release-4.18

[openshift-cherrypick-robot]

@cajieh: new pull request created: #16803

Details

In response to this:

/cherry-pick release-4.18

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.