Skip to content

DFBUGS-5033: [release-4.21] add check to avoid replicating terminating pvc#372

Merged
openshift-merge-bot[bot] merged 1 commit intored-hat-storage:release-4.21from
Nikhil-Ladha:dfbugs-5033/pvc-deleting
Jan 9, 2026
Merged

DFBUGS-5033: [release-4.21] add check to avoid replicating terminating pvc#372
openshift-merge-bot[bot] merged 1 commit intored-hat-storage:release-4.21from
Nikhil-Ladha:dfbugs-5033/pvc-deleting

Conversation

@Nikhil-Ladha
Copy link
Member

add check to avoid PVCs that are already in terminating state to be a part of VR/VGR.

(cherry picked from commit 4d0f688)

add check to avoid PVCs that are already in terminating state
to be a part of VR/VGR.

Signed-off-by: Nikhil-Ladha <nikhilladha1999@gmail.com>
(cherry picked from commit 4d0f688)
@openshift-ci-robot openshift-ci-robot added jira/valid-reference jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting labels Jan 8, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 8, 2026

@Nikhil-Ladha: This pull request references [Jira Issue DFBUGS-5033](https://issues.redhat.com//browse/DFBUGS-5033), which is valid.

2 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @keesturam

Details

In response to this:

add check to avoid PVCs that are already in terminating state to be a part of VR/VGR.

(cherry picked from commit 4d0f688)

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 label Jan 8, 2026
@openshift-ci openshift-ci bot requested a review from keesturam January 8, 2026 10:55
@Nikhil-Ladha
Copy link
Member Author

/cherry-pick release-4.20

@openshift-cherrypick-robot

@Nikhil-Ladha: once the present PR merges, I will cherry-pick it on top of release-4.20 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-4.20

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.

@Nikhil-Ladha Nikhil-Ladha requested a review from a team January 8, 2026 10:56
@Madhu-1
Copy link
Member

Madhu-1 commented Jan 9, 2026

/lgtm
/approve

@openshift-ci
Copy link

openshift-ci bot commented Jan 9, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Madhu-1, Nikhil-Ladha

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:
  • OWNERS [Madhu-1,Nikhil-Ladha]

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 6b4bd34 into red-hat-storage:release-4.21 Jan 9, 2026
12 checks passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 9, 2026

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

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

Details

In response to this:

add check to avoid PVCs that are already in terminating state to be a part of VR/VGR.

(cherry picked from commit 4d0f688)

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

@Nikhil-Ladha: new pull request created: #373

Details

In response to this:

/cherry-pick release-4.20

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting jira/valid-reference lgtm

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants