-
Notifications
You must be signed in to change notification settings - Fork 1.4k
🐛 Wait for volume detach after node drain #4945
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
🐛 Wait for volume detach after node drain #4945
Conversation
Hi @jzhoucliqr. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
5bbf0cf
to
f2859bb
Compare
f2859bb
to
2d98f66
Compare
2d98f66
to
2d0b68a
Compare
/test pull-cluster-api-test-main |
2d0b68a
to
d3e214f
Compare
/test pull-cluster-api-test-main |
4010207
to
6e2491e
Compare
How do we give some sort of timeout? What if a Volume never gets detached? Adding this in without a timeout can be considered a behavioral change on deletion, although I do agree that's probably more correct to wait for all volumes to be fully detached I'd like to make sure we have enough agreement on this change. |
@vincepri shouldn't |
That's true, I just saw that this code is in the |
6e2491e
to
504e2a3
Compare
/test pull-cluster-api-test-main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vincepri 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 |
What this PR does / why we need it:
Pod deletion and volume detach happen asynchronously, so pod could be deleted before volume detached from the node
When deleting a machine, this could cause issues for some storage provisioner, for example, vsphere-volume this is problematic because if the node deleted before volume detaching success, then the underline VMDK will be deleted together with the Machine
This PR added a fix to wait for volume detach from the node after node draining.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #4707