Tim Gross 951661db04 CSI: resolve invalid claim states (#11890) ... * csi: resolve invalid claim states on read It's currently possible for CSI volumes to be claimed by allocations that no longer exist. This changeset asserts a reasonable state at the state store level by registering these nil allocations as "past claims" on any read. This will cause any pass through the periodic GC or volumewatcher to trigger the unpublishing workflow for those claims. * csi: make feasibility check errors more understandable When the feasibility checker finds we have no free write claims, it checks to see if any of those claims are for the job we're currently scheduling (so that earlier versions of a job can't block claims for new versions) and reports a conflict if the volume can't be scheduled so that the user can fix their claims. But when the checker hits a claim that has a GCd allocation, the state is recoverable by the server once claim reaping completes and no user intervention is required; the blocked eval should complete. Differentiate the scheduler error produced by these two conditions.		2022-01-28 14:43:35 -05:00
..
benchmarks
annotate.go
annotate_test.go
context.go
context_test.go
device.go
device_test.go
feasible.go	CSI: resolve invalid claim states (#11890)	2022-01-28 14:43:35 -05:00
feasible_test.go
generic_sched.go
generic_sched_test.go
preemption.go
preemption_test.go
propertyset.go
rank.go
rank_test.go
reconcile.go
reconcile_test.go
reconcile_util.go
reconcile_util_test.go
scheduler.go
scheduler_oss.go
scheduler_sysbatch_test.go
scheduler_system.go
scheduler_system_test.go
select.go
select_test.go
spread.go
spread_test.go
stack.go
stack_oss.go
stack_test.go
testing.go
util.go
util_test.go