open-nomad/nomad/volumewatcher
Tim Gross 52e805a6a6
csi: ensure Read/WriteAllocs aren't released early (#7841)
We should only remove the `ReadAllocs`/`WriteAllocs` values for a
volume after the claim has entered the "ready to free"
state. The volume will eventually be released as expected. But
querying the volume API will show the volume is released before the
controller unpublish has finished and this can cause a race with
starting new jobs.

Test updates are to cover cases where we're dropping claims but not
running through the whole reaping process.
2020-04-30 17:11:31 -04:00
..
batcher.go csi: move volume claim release into volumewatcher (#7794) 2020-04-30 09:13:00 -04:00
batcher_test.go csi: move volume claim release into volumewatcher (#7794) 2020-04-30 09:13:00 -04:00
interfaces.go csi: move volume claim release into volumewatcher (#7794) 2020-04-30 09:13:00 -04:00
interfaces_test.go csi: move volume claim release into volumewatcher (#7794) 2020-04-30 09:13:00 -04:00
volume_watcher.go csi: move volume claim release into volumewatcher (#7794) 2020-04-30 09:13:00 -04:00
volume_watcher_test.go csi: move volume claim release into volumewatcher (#7794) 2020-04-30 09:13:00 -04:00
volumes_watcher.go csi: move volume claim release into volumewatcher (#7794) 2020-04-30 09:13:00 -04:00
volumes_watcher_test.go csi: ensure Read/WriteAllocs aren't released early (#7841) 2020-04-30 17:11:31 -04:00