Skip to content

OU-1134: edit perses dashboards automation testing #712

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
etmurasaki wants to merge 1 commit into
base: main
Choose a base branch
from
Open

OU-1134: edit perses dashboards automation testing #712

etmurasaki wants to merge 1 commit into from

Conversation

@etmurasaki
Copy link
Contributor

@etmurasaki etmurasaki commented Dec 29, 2025 •
edited
Loading

image

image used: 'quay.io/rh-ee-pyurkovi/observability-operator-bundle:1.4.6'

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 29, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 29, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 29, 2025

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

@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 29, 2025 •
edited by openshift-ci bot
Loading

@etmurasaki: This pull request references OU-1134 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 task to target the "4.22.0" version, but no target version was set.

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.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 29, 2025
@etmurasaki etmurasaki force-pushed the etmura-ou-1134 branch 2 times, most recently from 861fc2b to a80b798 Compare January 6, 2026 03:49
@etmurasaki etmurasaki marked this pull request as ready for review January 12, 2026 09:18
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 12, 2026
@etmurasaki
Copy link
Contributor Author

etmurasaki commented Jan 12, 2026

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 12, 2026
@etmurasaki etmurasaki force-pushed the etmura-ou-1134 branch 2 times, most recently from 6c68844 to 10857b0 Compare January 14, 2026 01:50
@etmurasaki
Copy link
Contributor Author

etmurasaki commented Jan 14, 2026

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 14, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 14, 2026 •
edited by openshift-ci bot
Loading

@etmurasaki: This pull request references OU-1134 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 task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

image

image used: 'quay.io/rh-ee-pyurkovi/observability-operator-bundle:1.4.6'

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.

@etmurasaki
Copy link
Contributor Author

etmurasaki commented Jan 14, 2026

/test ?

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 14, 2026

@etmurasaki: The following commands are available to trigger required jobs:

/test e2e-aws-ovn

/test images

/test lint

/test okd-scos-images

/test periodics-images

/test translations

/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-alerts

/test e2e-aws-ovn-upgrade

/test e2e-coo

/test e2e-dashboards

/test e2e-hypershift-conformance

/test e2e-incidents

/test e2e-metrics

/test e2e-monitoring

/test e2e-monitoring-bvt

/test e2e-monitoring-dev

/test e2e-monitoring-reg

/test e2e-virtualization

/test okd-scos-e2e-aws-ovn

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-monitoring-plugin-main-e2e-aws-ovn

pull-ci-openshift-monitoring-plugin-main-e2e-monitoring

pull-ci-openshift-monitoring-plugin-main-images

pull-ci-openshift-monitoring-plugin-main-lint

pull-ci-openshift-monitoring-plugin-main-okd-scos-images

pull-ci-openshift-monitoring-plugin-main-periodics-images

pull-ci-openshift-monitoring-plugin-main-translations

pull-ci-openshift-monitoring-plugin-main-verify-deps
Details

In response to this:

/test ?

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.

@etmurasaki
Copy link
Contributor Author

etmurasaki commented Jan 14, 2026

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Jan 14, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 14, 2026 •
edited by openshift-ci bot
Loading

@etmurasaki: This pull request references OU-1134 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 task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

image

image used: 'quay.io/rh-ee-pyurkovi/observability-operator-bundle:1.4.6'

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.

@etmurasaki
Copy link
Contributor Author

etmurasaki commented Jan 14, 2026

/test e2e-coo

2 similar comments
@etmurasaki
Copy link
Contributor Author

etmurasaki commented Jan 14, 2026

/test e2e-coo

@etmurasaki
Copy link
Contributor Author

etmurasaki commented Jan 14, 2026

/test e2e-coo

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 14, 2026

@etmurasaki: The following test 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-coo 01ad4ea link false /test e2e-coo

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.

jgbernalp
jgbernalp reviewed Jan 14, 2026
View reviewed changes
jgbernalp
jgbernalp reviewed Jan 14, 2026
View reviewed changes
@etmurasaki
Copy link
Contributor Author

etmurasaki commented Jan 14, 2026

/test e2e-coo

@etmurasaki
Copy link
Contributor Author

etmurasaki commented Jan 14, 2026

@jgbernalp could you please take a look again? Thank you!

@jgbernalp
Copy link
Contributor

jgbernalp commented Jan 14, 2026

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 14, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 14, 2026

[APPROVALNOTIFIER] This PR is APPROVED

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

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

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

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

Reviewers

@jgbernalp jgbernalp jgbernalp left review comments

@PeterYurkovich PeterYurkovich Awaiting requested review from PeterYurkovich

Assignees

@jgbernalp jgbernalp

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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@etmurasaki @openshift-ci-robot @jgbernalp