Skip to content

Conversation

@ShravaniVangur
Copy link
Contributor

Reverts #353

Reason: It has been merged for 4.17.7 but has been acked for 4.17.9. Have to push it to the right stream.

@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid jira ticket of any type jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting labels Jun 13, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 13, 2025

@ShravaniVangur: This pull request references [Jira Issue DFBUGS-2365](https://issues.redhat.com//browse/DFBUGS-2365), 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.

Details

In response to this:

Reverts #353

Reason: It has been merged for 4.17.7 but has been acked for 4.17.9. Have to push it to the right stream.

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.

@ShravaniVangur
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting label Jun 16, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 16, 2025

@ShravaniVangur: This pull request references [Jira Issue DFBUGS-2365](https://issues.redhat.com//browse/DFBUGS-2365), which is valid. The bug has been moved to the POST state.

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

Requesting review from QA contact:
/cc @jilju

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.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting label Jun 16, 2025
@openshift-ci
Copy link

openshift-ci bot commented Jun 16, 2025

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: jilju.

Note that only red-hat-storage members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

@ShravaniVangur: This pull request references [Jira Issue DFBUGS-2365](https://issues.redhat.com//browse/DFBUGS-2365), which is valid. The bug has been moved to the POST state.

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

Requesting review from QA contact:
/cc @jilju

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.

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.

@leelavg
Copy link
Contributor

leelavg commented Jun 16, 2025

/lgtm

@openshift-ci
Copy link

openshift-ci bot commented Jun 16, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: leelavg, ShravaniVangur

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-merge-bot openshift-merge-bot bot merged commit 29f1428 into red-hat-storage:release-4.17 Jun 16, 2025
3 checks passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 16, 2025

@ShravaniVangur: [Jira Issue DFBUGS-2365](https://issues.redhat.com//browse/DFBUGS-2365): All pull requests linked via external trackers have merged:

[Jira Issue DFBUGS-2365](https://issues.redhat.com//browse/DFBUGS-2365) has been moved to the MODIFIED state.

Details

In response to this:

Reverts #353

Reason: It has been merged for 4.17.7 but has been acked for 4.17.9. Have to push it to the right stream.

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 jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that the 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 size/S

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants