Jan Safranek e2826626b1 Fixed persistent volume claim controllers processing an old volume ...

We should always load the newest version of the volume from APIserver before
processing it.

When PersistentVolumeProvisionerController.reconcileVolume() is called with the
same volume in short succession (e.g. the volume is created by a provisioner
and at the same time periodic check of all volumes is scheduled), the second
reconcileVolume() call gets an old copy of the volume as its parameter and
it does not see annotations updated by the previous call.

This may result in one volume being provisioned several times, creating orphan
volumes in the cloud.

The same error is in PersistentVolumeClaimBinder.syncVolume().

2016-02-01 10:44:31 +01:00

..

persistentvolume_claim_binder_controller_test.go

Fixed persistent volume claim controllers processing an old volume

2016-02-01 10:44:31 +01:00

persistentvolume_claim_binder_controller.go

Fixed persistent volume claim controllers processing an old volume

2016-02-01 10:44:31 +01:00

persistentvolume_index_test.go

Fixed race condition in pv binder

2015-11-12 13:55:09 -05:00

persistentvolume_provisioner_controller_test.go

Fixed persistent volume claim controllers processing an old volume

2016-02-01 10:44:31 +01:00

persistentvolume_provisioner_controller.go

Fixed persistent volume claim controllers processing an old volume

2016-02-01 10:44:31 +01:00

persistentvolume_recycler_controller_test.go

replacing handwritten client in several controllers

2016-01-31 15:42:02 -08:00

persistentvolume_recycler_controller.go

replacing handwritten client in several controllers

2016-01-31 15:42:02 -08:00

types.go

Add PV.Name to volume tags.

2016-01-04 12:28:02 +01:00