Skip to content

NO-JIRA: release-4.21 e2e-monitoring and e2e-coo working#904

Open
etmurasaki wants to merge 1 commit intoopenshift:release-4.21from
etmurasaki:etmura-421-fix
Open

NO-JIRA: release-4.21 e2e-monitoring and e2e-coo working#904
etmurasaki wants to merge 1 commit intoopenshift:release-4.21from
etmurasaki:etmura-421-fix

Conversation

@etmurasaki
Copy link
Copy Markdown
Contributor

@etmurasaki etmurasaki commented Apr 27, 2026

image

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 27, 2026
@openshift-ci-robot
Copy link
Copy Markdown

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

Details

In response to this:

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
Copy link
Copy Markdown

coderabbitai Bot commented Apr 27, 2026

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: 422b4572-bd07-4164-a408-43cabbc2eb5e

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 and usage tips.

@openshift-ci openshift-ci Bot requested review from jgbernalp and zhuje April 27, 2026 11:04
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 27, 2026
@etmurasaki
Copy link
Copy Markdown
Contributor Author

/test e2e-monitoring

@etmurasaki
Copy link
Copy Markdown
Contributor Author

/test e2e-coo

@etmurasaki
Copy link
Copy Markdown
Contributor Author

/test ?

fixing legacy dashboard
@etmurasaki
Copy link
Copy Markdown
Contributor Author

/test e2e-monitoring

1 similar comment
@etmurasaki
Copy link
Copy Markdown
Contributor Author

/test e2e-monitoring

@etmurasaki
Copy link
Copy Markdown
Contributor Author

/test e2e-monitoring-dev

@etmurasaki
Copy link
Copy Markdown
Contributor Author

/label qe-approved

@openshift-ci openshift-ci Bot added the qe-approved Signifies that QE has signed off on this PR label Apr 27, 2026
@PeterYurkovich
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 27, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 27, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: etmurasaki, PeterYurkovich

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 [PeterYurkovich,etmurasaki]

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

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 27, 2026

@etmurasaki: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-ovn 165d037 link true /test e2e-aws-ovn
ci/prow/e2e-coo 2e6fa09 link false /test e2e-coo
ci/prow/e2e-monitoring-dev 165d037 link false /test e2e-monitoring-dev

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants