Skip to content

Conversation

@DavidHurta
Copy link
Contributor

@DavidHurta DavidHurta commented Nov 4, 2025

The runbook URLs were added in openshift/cluster-version-operator#1036 (ClusterOperatorDown) and openshift/cluster-version-operator#1250 (ClusterVersionOperatorDown).

The verification was done in OCPBUGS-14246.

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 4, 2025
@openshift-ci-robot
Copy link

@DavidHurta: This pull request references Jira Issue OCPBUGS-14246, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead

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.

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 do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 4, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 4, 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

@DavidHurta
Copy link
Contributor Author

/test all

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 4, 2025
@openshift-ci-robot
Copy link

@DavidHurta: This pull request references Jira Issue OCPBUGS-14246, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jiajliu

In response to this:

The runbook URLs were added in openshift/cluster-version-operator#1036 (ClusterOperatorDown) and openshift/cluster-version-operator#1250 (ClusterVersionOperatorDown).

The verification was done in OCPBUGS-14246.

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 requested a review from jiajliu November 4, 2025 15:41
The missing ClusterOperatorDown runbook URL was addressed in [1].
The missing ClusterVersionOperatorDown runbook URL was addressed in [2].

[1]: openshift/cluster-version-operator#1036
[2]: openshift/cluster-version-operator#1250
@DavidHurta DavidHurta force-pushed the remove-ClusterVersionOperatorDown-exception branch from 5bbf326 to 6ffb61f Compare November 4, 2025 15:45
@DavidHurta DavidHurta changed the title OCPBUGS-14246: Remove CVO alerts missing runbooks exceptions OCPBUGS-14246: Remove exceptions for missing CVO alert runbook URLs Nov 4, 2025
@DavidHurta DavidHurta marked this pull request as ready for review November 4, 2025 15:47
@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 Nov 4, 2025
@simonpasquier
Copy link
Contributor

/approve
/verified by e2e tests

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 4, 2025
@openshift-ci-robot
Copy link

@simonpasquier: This PR has been marked as verified by e2e tests.

In response to this:

/approve
/verified by e2e tests

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 Nov 4, 2025
@simonpasquier
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 5, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 5, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DavidHurta, simonpasquier

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 2d22e87 and 2 for PR HEAD 6ffb61f in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 5, 2025

@DavidHurta: all tests passed!

Full PR test history. Your PR dashboard.

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-merge-bot openshift-merge-bot bot merged commit 4f47dc4 into openshift:main Nov 5, 2025
20 checks passed
@openshift-ci-robot
Copy link

@DavidHurta: Jira Issue OCPBUGS-14246: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-14246 has been moved to the MODIFIED state.

In response to this:

The runbook URLs were added in openshift/cluster-version-operator#1036 (ClusterOperatorDown) and openshift/cluster-version-operator#1250 (ClusterVersionOperatorDown).

The verification was done in OCPBUGS-14246.

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-merge-robot
Copy link
Contributor

Fix included in accepted release 4.21.0-0.nightly-2025-11-05-234508

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-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants