fail umount when delete deployment

[wuzl]

After utilize exiting on-premise MooseFS storage for your Kubernetes cluster kubectl create -f deployment.yaml, create a deployment cat /proc/mounts, then we get some new mount

+/var/lib/kubelet/pods/743c5dca-43d5-11e9-811f-1866daf4cfd0/volumes/kubernetes.io~secret/default-token-lzx7d
+/var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-5662bfb2-43d5-11e9-811f-1866daf4cfd0/globalmount
+/var/lib/kubelet/pods/743c5dca-43d5-11e9-811f-1866daf4cfd0/volumes/kubernetes.io~csi/pvc-5662bfb2-43d5-11e9-811f-1866daf4cfd0/mount
+/var/lib/docker/overlay2/3bedd9d4263fa4a4d09f1790e513a52054a434d37261c85b19c969c08bb98c40/merged
+/var/lib/docker/containers/c1f010eb59c9f05e09aba6c5d07710279474beeed8ffec7b6f70d8ec5d12597c/shm
+/var/lib/docker/overlay2/fbadb2bd74d171298ff95fb8252a8aa3cb1a5c2c41638472cac61dc0a8d3d861/merged
+/var/lib/docker/overlay2/eb25ab4ed13ff23788a02c7e1b908656d069f84621ab9ec185963fb90a825f4f/merged

kubectl delete -f deployment.yaml, after delete a deployment cat /proc/mounts, we can see moosefs can not be umount

-/var/lib/kubelet/pods/743c5dca-43d5-11e9-811f-1866daf4cfd0/volumes/kubernetes.io~secret/default-token-lzx7d
-/var/lib/docker/overlay2/3bedd9d4263fa4a4d09f1790e513a52054a434d37261c85b19c969c08bb98c40/merged
-/var/lib/docker/containers/c1f010eb59c9f05e09aba6c5d07710279474beeed8ffec7b6f70d8ec5d12597c/shm
-/var/lib/docker/overlay2/fbadb2bd74d171298ff95fb8252a8aa3cb1a5c2c41638472cac61dc0a8d3d861/merged
-/var/lib/docker/overlay2/eb25ab4ed13ff23788a02c7e1b908656d069f84621ab9ec185963fb90a825f4f/merged

[wuzl]

it seem the IsMounted code have been changed https://github.com/digitalocean/csi-digitalocean/commit/8a50f616af33897c4138aa0efba5ba5ca1702347 does it matter

[pkonopelko]

Hello, please check out the latest release we have pushed to the repository, retest and reopen the issue if needed. Thanks