-
Notifications
You must be signed in to change notification settings - Fork 146
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
fix: reduce mount lock to avoid volumeID collision issue #1642
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andyzhangx 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 |
/retest |
2 similar comments
/retest |
/retest |
/cherrypick release-1.29 |
/cherrypick release-1.28 |
@andyzhangx: new pull request created: #1643 In response to this:
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. |
@andyzhangx: new pull request created: #1644 In response to this:
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. |
What type of PR is this?
/kind bug
What this PR does / why we need it:
fix: reduce mount lock to avoid volumeID collision issue
the volumeHandle(volumeID) could be duplicated in PV, and duplicated volumeHandle(volumeID) is already allowed in latest k8s version, this PR reduces mount lock to avoid volumeID collision issue, the lock only happen when volumeID + stagingPath is the same
Which issue(s) this PR fixes:
Fixes #1620
Requirements:
Special notes for your reviewer:
Release note: