Patrick Ohly 25e3a961c3 rbdplugin: idempotent DeleteVolume ... When the initial DeleteVolume times out (as it does on slow clusters due to the low 10 second limit), the external-provisioner calls it again. The CSI standard requires the second call to succeed if the volume has been deleted in the meantime. This didn't work because DeleteVolume returned an error when failing to find the volume info file: rbdplugin: E1008 08:05:35.631783 1 utils.go:100] GRPC error: rbd: open err /var/lib/kubelet/plugins/csi-rbdplugin/controller/csi-rbd-622a252c-cad0-11e8-9112-deadbeef0101.json/open /var/lib/kubelet/plugins/csi-rbdplugin/controller/csi-rbd-622a252c-cad0-11e8-9112-deadbeef0101.json: no such file or directory The fix is to treat a missing volume info file as "volume already deleted" and return success. To detect this, the original os error must be wrapped, otherwise the caller of loadVolInfo cannot determine the root cause. Note that further work may be needed to make the driver really resilient, for example there are probably concurrency issues. But for now this fixes: #82		2018-10-09 12:08:56 +02:00
..
controllerserver.go	rbdplugin: idempotent DeleteVolume	2018-10-09 12:08:56 +02:00
identityserver.go	rbd: advertises PluginCapability_Service_CONTROLLER_SERVICE	2018-06-13 15:14:15 +08:00
nodeserver.go	Fix misspelling of "successfully"	2018-09-21 23:08:23 +09:00
rbd_attach.go	allow monitors be embedded in credential secret	2018-09-21 14:43:01 +00:00
rbd_util.go	rbdplugin: idempotent DeleteVolume	2018-10-09 12:08:56 +02:00
rbd.go	Refactoring using users	2018-08-09 22:07:00 +09:00