-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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 photon controller plugin to construct with correct PdID #37167
Fix photon controller plugin to construct with correct PdID #37167
Conversation
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.
LGTM. This need to be cherry picked to 1.5.x.
Can you add a note to PR how you tested the fix?
Bug fix ok for post-code-freeze merge. We are planning on lifting code freeze soon. If this gets merged before code freeze is lifted it will automatically be picked up otherwise it'll need to be cherry picked to 1.5. Keep an eye on the |
@brendandburns @rootfs @luomiao : we really need to get reviews for this or push it off to 1.6 |
LGTM. @jingxu97 can you review? |
@brendandburns @jingxu97 @rootfs |
The input variable of function ConstructVolumeSpec is the volume spec name instead of persistent disk ID. Previously the function directly construct new volume spec by assigning volume spec name to persistent disk ID, which will result in mismatching of mount path. The fix will find the pdID according to mount path and construct volume spec with the correct pdID.
fb3c1e1
to
c240042
Compare
@k8s-bot cvm gke e2e test this |
@k8s-bot test this issue: #IGNORE |
@k8s-bot unit test this |
@k8s-bot kops aws e2e test this |
@k8s-bot gci gce e2e test this |
@k8s-bot test this |
@k8s-bot test this issue kubernetes/test-infra#1253 (also, deleting spurious failure comments) |
Automatic merge from submit-queue |
…7-upstream-release-1.5 Automated cherry pick of #37167
What this PR does / why we need it:
This PR is to fix a mismatching of unmount path in photon volume plugin, which is resulted from the assigning volume spec name to persistent disk ID. Without this path, unmounting process is stalling in reconciler when a pod is deleted. Restart the same pod will see a mount failure because the previous unmounting is still going on.
The input variable of function ConstructVolumeSpec is the volume spec name instead of persistent disk ID. Previously the function directly construct new volume spec by assigning volume spec name to persistent disk ID, which will result in mismatching of mount path. The fix will find the pdID according to mount path and construct volume spec with the correct pdID.
I have tested the patch with back-to-back pod creation/deletion and mounting/unmounting of photon persistent disk volume source performs normal now.
This need to be cherry-picked to 1.5 release branch.
This change is