Steve Leon c1882d4760 Ensuring volume lock is released when the same pod is requesting it ...

There is a case where a pod is trying to request a volume
attachment after the previous attachment failed. However even though this is
the same pod as the original attachment request, its UID could be different. This is normally caused when
the user manually deletes the pod and recreate it again. The name will be the same but the ID will be different

fixes https://github.com/rook/rook/issues/1214

2017-12-01 13:34:30 -08:00

..

cluster

operator: update to latest operator kit with logging

2017-11-14 12:44:50 -08:00

flexvolume

Ensuring volume lock is released when the same pod is requesting it

2017-12-01 13:34:30 -08:00

agent.go

clean up outstanding rbd devices during cluster deletion

2017-11-03 17:43:54 -07:00