Description
Kubernetes version: 1.6
Component/Area: Storage
Affected modules: Flex volume
Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"6+", GitVersion:"v1.6.0-alpha.1.482+b2ea780731417d-dirty", GitCommit:"b2ea780731417da74d312bfce8ac560ae7248831", GitTreeState:"dirty", BuildDate:"2017-02-07T21:51:55Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"6+", GitVersion:"v1.6.1-1+00a638423087f6-dirty", GitCommit:"00a638423087f6e81819667f662f194a2a2d8da9", GitTreeState:"dirty", BuildDate:"2017-04-15T16:16:36Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}
What happened:
Flex volumes which implement getvolumename API are getting unmounted during run time.
What you expected to happen:
Volumes should not be unmounted.
How to reproduce it (as minimally and precisely as possible):
Use flex volume driver which implements getvolumename.
Anything else we need to know:
Workaround:
- Do not implement getvolumename API. The API default uses PV Name as the volume name.
- Detach call uses volume name, so the plugin detach has to work with PV Name.
Temporary fix for 1.6:
- Pass PV Name to flex volume driver using extra options.