Project

General

Profile

Actions

Bug #16219

closed

Selected node size with insufficient scratch space

Added by Peter Amstutz about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Crunch
Target version:
Story points:
-
Release relationship:
Auto

Actions #1

Updated by Peter Amstutz about 4 years ago

  • Description updated (diff)
Actions #2

Updated by Peter Amstutz about 4 years ago

  • Assigned To set to Tom Clegg
Actions #3

Updated by Tom Clegg about 4 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.

Actions #6

Updated by Tom Clegg about 4 years ago

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

Actions #7

Updated by Tom Clegg about 4 years ago

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

Updated by Tom Clegg about 4 years ago

  • Release set to 30
Actions #9

Updated by Anonymous about 4 years ago

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

Updated by Tom Clegg about 4 years ago

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

Updated by Tom Clegg about 4 years ago

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

Also available in: Atom PDF