Actions
Bug #16219
closedSelected node size with insufficient scratch space
Start date:
Due date:
% Done:
100%
Estimated time:
Story points:
-
Release:
Release relationship:
Auto
Updated by Tom Clegg almost 5 years ago
- Status changed from New to In Progress
Looks like dispatcher does not loading the mounts or container_image field when populating the container queue, and as a result the minimum scratch space is always computed to be 0.
Updated by Tom Clegg almost 5 years ago
16219-insufficient-scratch @ 643b160f9af9a245607d4cbee488d08f8516df5e -- developer-run-tests: #1766
Updated by Tom Clegg almost 5 years ago
16219-insufficient-scratch @ 12eec0fb0fc7cce9d012c81b44a9684ea45d6926 (updates test to check the relevant fields)
Updated by Tom Clegg almost 5 years ago
- Target version changed from 2020-03-25 Sprint to 2020-03-11 Sprint
Updated by Anonymous almost 5 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset arvados|26c62aa2c173b981f335580885f732a81611e89b.
Updated by Tom Clegg almost 5 years ago
- Related to Bug #16270: "constraints not satisfiable by any configured instance type " added
Updated by Tom Clegg almost 5 years ago
- Related to deleted (Bug #16270: "constraints not satisfiable by any configured instance type ")
Actions