-
Notifications
You must be signed in to change notification settings - Fork 729
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 PV path determination on deletion #323
base: master
Are you sure you want to change the base?
Conversation
|
Welcome @fruboes! |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: fruboes The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Dear @humblec and @ashishranjan738 - it looks this got somehow buried.. Could you have a look on this PR? |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
Determination of
oldPath
in Delete func seems to be broken. With my test pvc, I get following vars prior to path calculation:For the above vars, current implementation leads to
/persistentvolumesdefault/test-claim-1
being generated instead of/persistentvolumes/default/test-claim-1
. This PR fixes the issue by using filepath.Join instead of using strings.Replace exclusively.