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

..

crd

clean up outstanding rbd devices during cluster deletion

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

manager

Failover mon when there is more than one mon on one node

2017-11-10 16:35:58 +01:00

controller_test.go

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

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

controller.go

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

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

fake.go

clean up outstanding rbd devices during cluster deletion

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

server_test.go

Renaming flexvolume to rookflex

2017-10-12 13:19:55 -07:00

server.go

clean up outstanding rbd devices during cluster deletion

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

types.go

clean up outstanding rbd devices during cluster deletion

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