Project

General

Profile

Actions

Bug #5388

closed

[Crunch] Jobs do not re-run with latest docker image if job is unchanged but docker image is updated

Added by Abram Connelly over 7 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Brett Smith
Category:
API
Target version:
Start date:
03/05/2015
Due date:
% Done:

100%

Estimated time:
Story points:
-

Description

I successfully ran a job with a docker image of my own making called 'arvados/dax-node'. I did not alter the job but updated the docker image and re-uploaded it via 'arv-keepdocker' (with the same name 'arvados/dax-node'). After the new docker image was uploaded and the job re-run, the job completed immediately (successfully) presumably because it thought nothing had changed.

Looking at the docker image used in the job, it was the old docker image and not the new one.

Specifically, the pipeline instance run was 'tb05z-d1hrv-hbgo72pe87pj7er'. The new docker image ('arvados/dax-node', 'latest') was 'tb05z-4zz18-nslhjho8iyq29am' but the job used an older docker image (also named 'arvados/dax-node', 'latest') with UUID 'tb05z-4zz18-yog9g7dk10ooxjk'.

The workaround is easy enough, just 'dirty' the pipeline in some way, either by forcing a re-run or updating the git repository.


Related issues

Related to Arvados - Bug #5490: [Crunch] Job should not be reused when docker tag _or_ arvados sdk version now resolves to a different image/commitResolvedBrett Smith04/21/2015

Actions
Actions #1

Updated by Abram Connelly over 7 years ago

I should mention that I'm submitting the job via the CLI tool 'arv-run-pipeline-instance':

arv-run-pipeline-instance --submit --template <( echo "$template" ) $opt
Actions #2

Updated by Tom Clegg over 7 years ago

  • Category set to API
  • Story points set to 1.0
Actions #3

Updated by Peter Amstutz over 7 years ago

  • Target version changed from Bug Triage to 2015-04-29 sprint
Actions #4

Updated by Tom Clegg about 7 years ago

  • Subject changed from Jobs do not re-run with latest docker image if job is unchanged but docker image is updated to [Crunch] Jobs do not re-run with latest docker image if job is unchanged but docker image is updated
Actions #5

Updated by Tom Clegg about 7 years ago

  • Story points deleted (1.0)
Actions #6

Updated by Brett Smith about 7 years ago

  • Assigned To set to Brett Smith
Actions #7

Updated by Brett Smith about 7 years ago

Diagnosing this specific pipeline may be complicated by #5752.

Actions #8

Updated by Brett Smith about 7 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Applied in changeset arvados|commit:03d89302f14a4a1c448b32d62679bab14e23fa23.

Actions

Also available in: Atom PDF