Skip to content

[release-4.21] OCPBUGS-77655: feat(node-deletion): remove stale LVMVolumeGroup finalizers#2075

Merged
suleymanakbas91 merged 1 commit intoopenshift:release-4.21from
openshift-cherrypick-robot:cherry-pick-2073-to-release-4.21
Mar 3, 2026
Merged

[release-4.21] OCPBUGS-77655: feat(node-deletion): remove stale LVMVolumeGroup finalizers#2075
suleymanakbas91 merged 1 commit intoopenshift:release-4.21from
openshift-cherrypick-robot:cherry-pick-2073-to-release-4.21

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #2073

/assign qJkee

remove LVMVolumeGroup node finalizer when node is being deleted
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-76993 has been cloned as Jira Issue OCPBUGS-77655. Will retitle bug to link to clone.
/retitle [release-4.21] OCPBUGS-77655: feat(node-deletion): remove stale LVMVolumeGroup finalizers

Details

In response to this:

This is an automated cherry-pick of #2073

/assign qJkee

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 changed the title [release-4.21] OCPBUGS-76993: feat(node-deletion): remove stale LVMVolumeGroup finalizers [release-4.21] OCPBUGS-77655: feat(node-deletion): remove stale LVMVolumeGroup finalizers Mar 3, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important 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 a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 3, 2026
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-77655, 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 dependent Jira Issue OCPBUGS-76993 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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.

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

/assign qJkee

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 size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Mar 3, 2026
@openshift-ci openshift-ci bot requested review from jaypoulz and qJkee March 3, 2026 12:15
@qJkee
Copy link
Contributor

qJkee commented Mar 3, 2026

/lgtm
/approve

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

openshift-ci bot commented Mar 3, 2026

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Mar 3, 2026
@suleymanakbas91 suleymanakbas91 merged commit 31c4236 into openshift:release-4.21 Mar 3, 2026
3 of 4 checks passed
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-77655: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-77655 has been moved to the MODIFIED state.

Details

In response to this:

This is an automated cherry-pick of #2073

/assign qJkee

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.

@qJkee
Copy link
Contributor

qJkee commented Mar 12, 2026

/cherry-pick release-4.20

@openshift-cherrypick-robot
Copy link
Author

@qJkee: new pull request created: #2129

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 Indicates a PR has been approved by an approver from all required OWNERS files. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-important Referenced Jira bug's severity is important 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. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants