Skip to content

Conversation

@locriandev
Copy link

No description provided.

@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 Jan 28, 2026
@openshift-ci-robot
Copy link

@locriandev: This pull request references Jira Issue OCPBUGS-74168, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-74168 to depend on a bug targeting a version in 4.23.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, 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:

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 review from Elbehery and dusk125 January 28, 2026 16:42
@dusk125
Copy link

dusk125 commented Jan 28, 2026

/lgtm

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 28, 2026
@dusk125
Copy link

dusk125 commented Jan 28, 2026

/cherry-pick openshift-4.21

@openshift-cherrypick-robot

@dusk125: once the present PR merges, I will cherry-pick it on top of openshift-4.21 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick openshift-4.21

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.

@dusk125
Copy link

dusk125 commented Jan 28, 2026

This is the same as #355, but targeting 4.22 instead of main since our main branch isn't set up properly

@dusk125
Copy link

dusk125 commented Jan 30, 2026

/retest

@dusk125
Copy link

dusk125 commented Jan 30, 2026

/label backport-risk-assessed
/retest
I think this failure is unrelated, but seeing if I can get a non-flake before overriding

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jan 30, 2026
@tjungblu
Copy link

tjungblu commented Feb 2, 2026

/retest-required

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 3, 2026
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 3, 2026
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 3, 2026
@dusk125
Copy link

dusk125 commented Feb 3, 2026

/lgtm

@openshift-ci
Copy link

openshift-ci bot commented Feb 3, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dusk125, locriandev

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:

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

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 3, 2026
@dusk125
Copy link

dusk125 commented Feb 3, 2026

/retest-required

@openshift-ci
Copy link

openshift-ci bot commented Feb 3, 2026

@locriandev: 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 648bd0b link true /test e2e-aws-ovn
ci/prow/configmap-scale 648bd0b link true /test configmap-scale
ci/prow/unit 648bd0b link true /test unit
ci/prow/e2e-aws-ovn-upgrade 648bd0b link true /test e2e-aws-ovn-upgrade
ci/prow/images 648bd0b link true /test images
ci/prow/e2e-aws-ovn-serial 648bd0b link true /test e2e-aws-ovn-serial

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/invalid-bug Indicates that a referenced Jira bug is invalid 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants