Bug #16219

Selected node size with insufficient scratch space

Added by Peter Amstutz 3 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Crunch
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Story points:
-
Release relationship:
Auto

Associated revisions

Revision 26c62aa2
Added by Tom Clegg 3 months ago

Merge branch '16219-insufficient-scratch'

fixes #16219

Arvados-DCO-1.1-Signed-off-by: Tom Clegg <>

History

#1 Updated by Peter Amstutz 3 months ago

  • Description updated (diff)

#2 Updated by Peter Amstutz 3 months ago

  • Assigned To set to Tom Clegg

#3 Updated by Tom Clegg 3 months 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.

#6 Updated by Tom Clegg 3 months ago

16219-insufficient-scratch @ 12eec0fb0fc7cce9d012c81b44a9684ea45d6926 (updates test to check the relevant fields)

#7 Updated by Tom Clegg 3 months ago

  • Target version changed from 2020-03-25 Sprint to 2020-03-11 Sprint

#8 Updated by Tom Clegg 3 months ago

  • Release set to 30

#9 Updated by Anonymous 3 months ago

  • % Done changed from 0 to 100
  • Status changed from In Progress to Resolved

#10 Updated by Tom Clegg 2 months ago

  • Related to Bug #16270: "constraints not satisfiable by any configured instance type " added

#11 Updated by Tom Clegg 2 months ago

  • Related to deleted (Bug #16270: "constraints not satisfiable by any configured instance type ")

Also available in: Atom PDF