Project

General

Profile

Actions

Bug #5990

closed

[SDKs] arv-run defaults to using arvados/jobs, without checking that it exists or is recent

Added by Brett Smith almost 9 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
SDKs
Target version:
Story points:
0.5

Description

This can lead to pipeline failures that are mysterious to users, if arvados/jobs does not exist or has an SDK that's too old to run a current run-command.

Once #3454 is done and deployed, we may be able to rely on that, and take the default Docker image out of arv-run completely.


Subtasks 3 (0 open3 closed)

Task #6105: Review 5990-arv-run-default-runtimeResolvedPeter Amstutz05/25/201505/25/2015Actions
Task #6722: FixResolvedPeter Amstutz05/25/2015Actions
Task #6734: Update docsResolvedPeter Amstutz05/25/2015Actions

Related issues

Related to Arvados - Feature #3454: [API] Assign a system-default default docker image (instead of using the non-docker code path) if none is specified in runtime_constraints.ResolvedRadhika Chippada05/07/2015Actions
Follows (1 day) Arvados - Idea #6096: [OPS] Implement a process to regularly deploy a Docker image for running jobs to Arvados clustersResolvedWard Vandewege05/22/2015Actions
Actions

Also available in: Atom PDF