Bug #12349

[API] Validate container requests "output_path must be in a writable mount"

Added by Tom Clegg over 4 years ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
API
Target version:
-
Start date:
09/27/2017
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

If output_path is not in a writable mount, crunch-run will cancel the container with a suitable error message (see #12298). But this means waiting (and perhaps paying) to bring up a compute node, only to check something that could be checked instantly by the API when committing the container request.

Proposed fix:

Check this when saving a container request (perhaps only when saving with state=Committed). If this error is detected, fail the create/update request.


Related issues

Related to Arvados - Bug #12298: [Crunch2] Invalid container output_path causes infinite loop of futile dispatch attemptsResolved09/20/2017

Also available in: Atom PDF