Skip to content

OCPBUGS-76993: feat(node-deletion): remove stale LVMVolumeGroup finalizers#2073

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
qJkee:OCPBUGS-76993
Mar 2, 2026
Merged

OCPBUGS-76993: feat(node-deletion): remove stale LVMVolumeGroup finalizers#2073
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
qJkee:OCPBUGS-76993

Conversation

@qJkee
Copy link
Contributor

@qJkee qJkee commented Mar 2, 2026

remove LVMVolumeGroup node finalizer when node is being deleted

remove LVMVolumeGroup node finalizer when node is being deleted
@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 2, 2026
@openshift-ci-robot
Copy link

@qJkee: This pull request references Jira Issue OCPBUGS-76993, which is invalid:

  • expected the bug to target the "4.22.0" version, but no target version was set

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:

remove LVMVolumeGroup node finalizer when node is being deleted

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 requested review from jerpeter1 and pacevedom March 2, 2026 07:34
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 2, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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 size/L Denotes a PR that changes 100-499 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 2, 2026
@codecov-commenter
Copy link

Codecov Report

❌ Patch coverage is 75.00000% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 49.39%. Comparing base (dc4e41c) to head (99e6ad9).
⚠️ Report is 6 commits behind head on main.

Files with missing lines Patch % Lines
internal/controllers/node/removal/controller.go 75.00% 1 Missing and 2 partials ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #2073      +/-   ##
==========================================
+ Coverage   49.16%   49.39%   +0.22%     
==========================================
  Files          52       52              
  Lines        3777     3778       +1     
==========================================
+ Hits         1857     1866       +9     
+ Misses       1767     1759       -8     
  Partials      153      153              
Files with missing lines Coverage Δ
internal/controllers/node/removal/controller.go 81.15% <75.00%> (+12.04%) ⬆️
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 2, 2026

@qJkee: 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.

@suleymanakbas91
Copy link
Contributor

/lgtm

@suleymanakbas91
Copy link
Contributor

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Mar 2, 2026
@openshift-ci-robot
Copy link

@suleymanakbas91: This pull request references Jira Issue OCPBUGS-76993, 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 (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @mmakwana30

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 a referenced Jira bug is invalid for the branch this PR is targeting. label Mar 2, 2026
@openshift-ci openshift-ci bot requested a review from mmakwana30 March 2, 2026 18:07
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 2, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit 54fe522 into openshift:main Mar 2, 2026
14 checks passed
@openshift-ci-robot
Copy link

@qJkee: Jira Issue OCPBUGS-76993: All pull requests linked via external trackers have merged:

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

Details

In response to this:

remove LVMVolumeGroup node finalizer when node is being deleted

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 Author

qJkee commented Mar 3, 2026

/cherry-pick release-4.21

@openshift-cherrypick-robot

@qJkee: new pull request created: #2075

Details

In response to this:

/cherry-pick release-4.21

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/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. 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. 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.

5 participants