You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A volume that has access_mode = "single-node-reader-only" or access_mode = "single-node-writer" is feasibility checked during scheduling to ensure that only a single reader or writer claim exists. However, because feasibility checking is done one alloc at a time before the plan is written, a job that's misconfigured to have count > 1 that mounts one of these volumes will pass feasibility checking. The first allocation will be placed, but if the storage provider enforces its invariants the second and later allocations will fail after placement on the client.
To reproduce, use this volume specification with the hostpath plugin (with the UUID value set from the ID returned from csc):
Note that the hostpath plugin is a toy plugin and does not enforce its invariants, so you'll see two allocations merrily scheduled to use the volume that's been marked for single reader.
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
A volume that has
access_mode = "single-node-reader-only"
oraccess_mode = "single-node-writer"
is feasibility checked during scheduling to ensure that only a single reader or writer claim exists. However, because feasibility checking is done one alloc at a time before the plan is written, a job that's misconfigured to havecount
> 1 that mounts one of these volumes will pass feasibility checking. The first allocation will be placed, but if the storage provider enforces its invariants the second and later allocations will fail after placement on the client.To reproduce, use this volume specification with the hostpath plugin (with the UUID value set from the ID returned from
csc
):And this job specification:
Note that the hostpath plugin is a toy plugin and does not enforce its invariants, so you'll see two allocations merrily scheduled to use the volume that's been marked for single reader.
Discovered this while writing tests for #10136
The text was updated successfully, but these errors were encountered: