Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCPVE-677: chore: change finalizer logic in vgmanager to per-node finalizer #408

Conversation

jakobmoellerdev
Copy link
Contributor

Part of findings during vgmanager testing. Changes the finalizer logic of vgmanager to the following:

  • "lvm.openshift.io/lvmvolumegroup" gets deprecated and if found on existing volumegroups, it will be removed
  • "cleanup.vgmanager.node.topolvm.io/$NODE_NAME" gets introduced for every node interacting with the volume group and only removed once processDelete is successful. If all nodes successfully delete vg, the VolumeGroup should not have any other finalizers and may be dropped.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 8, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 8, 2023

@jakobmoellerdev: This pull request references OCPVE-677 which is a valid jira issue.

In response to this:

Part of findings during vgmanager testing. Changes the finalizer logic of vgmanager to the following:

  • "lvm.openshift.io/lvmvolumegroup" gets deprecated and if found on existing volumegroups, it will be removed
  • "cleanup.vgmanager.node.topolvm.io/$NODE_NAME" gets introduced for every node interacting with the volume group and only removed once processDelete is successful. If all nodes successfully delete vg, the VolumeGroup should not have any other finalizers and may be dropped.

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/test-infra repository.

@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Sep 8, 2023
@jakobmoellerdev
Copy link
Contributor Author

/retest-required

@suleymanakbas91
Copy link
Contributor

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 8, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 8, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jakobmoellerdev, suleymanakbas91

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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 Sep 8, 2023
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 8da92ee and 2 for PR HEAD 25b32cc in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ceed42e and 1 for PR HEAD 25b32cc in total

@codecov-commenter
Copy link

codecov-commenter commented Sep 8, 2023

Codecov Report

Merging #408 (4b7a879) into main (8da92ee) will decrease coverage by 0.42%.
Report is 4 commits behind head on main.
The diff coverage is 30.00%.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main     #408      +/-   ##
==========================================
- Coverage   55.01%   54.59%   -0.42%     
==========================================
  Files          27       27              
  Lines        2341     2337       -4     
==========================================
- Hits         1288     1276      -12     
- Misses        965      974       +9     
+ Partials       88       87       -1     
Files Changed Coverage Δ
pkg/vgmanager/vgmanager_controller.go 9.24% <0.00%> (-0.25%) ⬇️
controllers/lvm_volumegroup.go 79.66% <54.54%> (-2.03%) ⬇️

... and 1 file with indirect coverage changes

@jakobmoellerdev
Copy link
Contributor Author

/test lvm-operator-e2e-aws

@jakobmoellerdev
Copy link
Contributor Author

/test lvm-operator-e2e-aws-sno

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 8fce2eb and 0 for PR HEAD 25b32cc in total

@jakobmoellerdev jakobmoellerdev force-pushed the OCPVE-677-finalizer-refactor branch from 25b32cc to 4b7a879 Compare September 8, 2023 17:08
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Sep 8, 2023
@suleymanakbas91
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 8, 2023
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 3386fe2 and 2 for PR HEAD 4b7a879 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 8208b3a and 1 for PR HEAD 4b7a879 in total

@jakobmoellerdev jakobmoellerdev force-pushed the OCPVE-677-finalizer-refactor branch from 4b7a879 to fc4da02 Compare September 8, 2023 20:19
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Sep 8, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 8, 2023

@jakobmoellerdev: all tests passed!

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

@suleymanakbas91
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 11, 2023
@openshift-merge-robot openshift-merge-robot merged commit 1ba3a1c into openshift:main Sep 11, 2023
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/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/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants