Skip to content

Conversation

@gnufied
Copy link
Member

@gnufied gnufied commented Jan 27, 2026

@openshift-ci-robot openshift-ci-robot added backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jan 27, 2026
@openshift-ci-robot
Copy link

@gnufied: This pull request references Jira Issue OCPBUGS-74530, which is valid.

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

No GitHub users were found matching the public email listed for the QA contact in Jira (wduan@redhat.com), skipping review request.

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

Details

In response to this:

fixes https://issues.redhat.com/browse/OCPBUGS-74530

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

@gnufied: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@gnufied gnufied force-pushed the remove-storage-performant-policy branch from 928557d to ac90590 Compare January 27, 2026 21:19
@openshift-ci-robot
Copy link

@gnufied: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@JoelSpeed
Copy link

/lgtm

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

gnufied commented Jan 28, 2026

Failures look unrelated to the change.

/retest-required

@benluddy
Copy link

/approve
/remove-label backports/unvalidated-commits

@openshift-ci openshift-ci bot removed the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Jan 28, 2026
@openshift-ci
Copy link

openshift-ci bot commented Jan 28, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: benluddy, gnufied, JoelSpeed

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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 28, 2026
@gnufied
Copy link
Member Author

gnufied commented Jan 28, 2026

/retest-required

2 similar comments
@gnufied
Copy link
Member Author

gnufied commented Jan 29, 2026

/retest-required

@gnufied
Copy link
Member Author

gnufied commented Jan 29, 2026

/retest-required

@JoelSpeed
Copy link

/verified by E2E

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 30, 2026
@openshift-ci-robot
Copy link

@JoelSpeed: This PR has been marked as verified by E2E.

Details

In response to this:

/verified by E2E

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

/retest-required

Remaining retests: 0 against base HEAD 0a955cc and 2 for PR HEAD ac90590 in total

@gnufied
Copy link
Member Author

gnufied commented Jan 30, 2026

/retest-required

@openshift-ci
Copy link

openshift-ci bot commented Jan 30, 2026

@gnufied: 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/k8s-e2e-conformance-aws ac90590 link true /test k8s-e2e-conformance-aws
ci/prow/k8s-e2e-gcp-serial ac90590 link true /test k8s-e2e-gcp-serial
ci/prow/e2e-aws-ovn-cgroupsv2 ac90590 link true /test e2e-aws-ovn-cgroupsv2
ci/prow/images ac90590 link true /test images
ci/prow/e2e-aws-ovn-serial-1of2 ac90590 link true /test e2e-aws-ovn-serial-1of2
ci/prow/k8s-e2e-gcp-ovn ac90590 link true /test k8s-e2e-gcp-ovn
ci/prow/e2e-aws-crun-wasm ac90590 link true /test e2e-aws-crun-wasm
ci/prow/e2e-aws-ovn-runc ac90590 link true /test e2e-aws-ovn-runc
ci/prow/e2e-aws-ovn-crun ac90590 link true /test e2e-aws-ovn-crun
ci/prow/e2e-aws-ovn-serial-2of2 ac90590 link true /test e2e-aws-ovn-serial-2of2
ci/prow/e2e-aws-ovn-fips ac90590 link true /test e2e-aws-ovn-fips
ci/prow/e2e-aws-ovn-hypershift ac90590 link true /test e2e-aws-ovn-hypershift
ci/prow/e2e-metal-ipi-ovn-ipv6 ac90590 link true /test e2e-metal-ipi-ovn-ipv6

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-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