Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #475

/assign radeore

@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 19, 2025

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: STOR-2543

Details

In response to this:

This is an automated cherry-pick of #475

/assign radeore

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.

@radeore
Copy link

radeore commented Dec 22, 2025

/retest-required

@mpatlasov
Copy link
Contributor

/retest-required
/override ci/prow/okd-scos-images
OKD has a known outage

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 6, 2026

@mpatlasov: Overrode contexts on behalf of mpatlasov: ci/prow/okd-scos-images

Details

In response to this:

/retest-required
/override ci/prow/okd-scos-images
OKD has a known outage

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.

@dfajmon
Copy link
Contributor

dfajmon commented Jan 20, 2026

/retest-required

@jsafrane
Copy link
Contributor

/lgtm
/approve
/label backport-risk-assessed

@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 20, 2026
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 20, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 20, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsafrane, openshift-cherrypick-robot

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 20, 2026
@radeore
Copy link

radeore commented Jan 20, 2026

/verified by CI

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

@radeore: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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.

@dfajmon
Copy link
Contributor

dfajmon commented Jan 20, 2026

/retitle STOR-2543: [release-4.21]: add VAC manifest for tests in AWS EBS

@openshift-ci openshift-ci bot changed the title [release-4.21] STOR-2543: add VAC manifest for tests in AWS EBS STOR-2543: [release-4.21]: add VAC manifest for tests in AWS EBS Jan 20, 2026
@dfajmon
Copy link
Contributor

dfajmon commented Jan 20, 2026

/refresh

@radeore
Copy link

radeore commented Jan 21, 2026

/retitle OCPBUGS-74215: [release-4.21] Add VAC manifest for tests in AWS EBS

@openshift-ci openshift-ci bot changed the title STOR-2543: [release-4.21]: add VAC manifest for tests in AWS EBS OCPBUGS-74215: [release-4.21] Add VAC manifest for tests in AWS EBS Jan 21, 2026
@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 21, 2026
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-74215, which is invalid:

  • expected the bug to target the "4.21.0" version, but no target version was set
  • 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-74215 to depend on a bug targeting a version in 4.22.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:

This is an automated cherry-pick of #475

/assign radeore

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.

@radeore
Copy link

radeore commented Jan 21, 2026

/jira refresh

@openshift-ci-robot
Copy link

@radeore: This pull request references Jira Issue OCPBUGS-74215, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead
  • expected Jira Issue OCPBUGS-74215 to depend on a bug targeting a version in 4.22.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.

Details

In response to this:

/jira refresh

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.

@radeore
Copy link

radeore commented Jan 21, 2026

/jira refresh

@openshift-ci-robot
Copy link

@radeore: This pull request references Jira Issue OCPBUGS-74215, which is invalid:

  • expected Jira Issue OCPBUGS-74215 to depend on a bug targeting a version in 4.22.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.

Details

In response to this:

/jira refresh

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.

@radeore
Copy link

radeore commented Jan 21, 2026

/jira refresh

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

@radeore: This pull request references Jira Issue OCPBUGS-74215, which is valid. The bug has been moved to the POST state.

7 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 ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-74213 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-74213 targets the "4.22.0" version, which is one of the valid target versions: 4.22.0
  • bug has dependents

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

Details

In response to this:

/jira refresh

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.

@radeore
Copy link

radeore commented Jan 21, 2026

/test e2e-aws-csi

@radeore
Copy link

radeore commented Jan 21, 2026

/test e2e-azure-csi

@radeore
Copy link

radeore commented Jan 21, 2026

/test e2e-aws-csi

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD d739d8c and 2 for PR HEAD f954b88 in total

@radeore
Copy link

radeore commented Jan 21, 2026

/retest-required

@radeore
Copy link

radeore commented Jan 21, 2026

/test e2e-aws-csi

1 similar comment
@radeore
Copy link

radeore commented Jan 21, 2026

/test e2e-aws-csi

@Phaow
Copy link
Contributor

Phaow commented Jan 22, 2026

/retest-required

1 similar comment
@radeore
Copy link

radeore commented Jan 22, 2026

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 22, 2026

@openshift-cherrypick-robot: all tests passed!

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.

@openshift-merge-bot openshift-merge-bot bot merged commit d3789c5 into openshift:release-4.21 Jan 22, 2026
21 checks passed
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-74215
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-74215 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

This is an automated cherry-pick of #475

/assign radeore

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.

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

9 participants