Project

General

Profile

Actions
Copy link

Bug #3698

closed

[Crunch] Pipeline runner should detect when "output_of" refers to a non-existent component, and fail instead of staying in RunningOnServer state forever.

Added by Peter Amstutz over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Peter Amstutz
Category:
Crunch
Target version:
2014-12-10 sprint
Story points:
0.5

Subtasks 4 (0 open — 4 closed)

Task #4715: Retest on qr1hi after deployResolved10/17/2014Actions
Task #4608: Investigate regressionResolvedPeter Amstutz10/17/2014Actions
Task #4257: Review 3698-invalid-output-ofResolvedPeter Amstutz10/17/2014Actions
Task #4145: Add validation that output_of links refer to existing componentsResolvedPeter Amstutz10/17/2014Actions

Related issues

Has duplicate Arvados - Bug #4200: [Crunch] Notify user, cancel pipeline when it cannot run because a parameter is the output_of a nonexistent componentClosed10/15/2014Actions
Has duplicate Arvados - Task #4171: [Crunch] arv-run-pipeline-instance should detect bad "output_of" values and fail the pipelineClosed10/09/2014Actions
Has duplicate Arvados - Bug #4064: [Crunch] Typoed "output_of" value in pipeline leaves a job stuck in the queueResolved10/09/2014Actions
Actions
Copy link
 #1

Updated by Peter Amstutz over 9 years ago

  • Subject changed from Pipeline runner doesn't detect when "output_of" refers to non-existent component, will stall instead of failing. to [Crunch] Pipeline runner doesn't detect when "output_of" refers to non-existent component, will stall instead of failing.
  • Category set to Crunch
Actions
Copy link
 #2

Updated by Peter Amstutz over 9 years ago

  • Target version set to Arvados Future Sprints
Actions
Copy link
 #3

Updated by Tom Clegg over 9 years ago

  • Subject changed from [Crunch] Pipeline runner doesn't detect when "output_of" refers to non-existent component, will stall instead of failing. to [Crunch] Pipeline runner should detect when "output_of" refers to a non-existent component, and fail instead of staying in RunningOnServer state forever.
  • Story points set to 0.5
Actions
Copy link
 #4

Updated by Ward Vandewege over 9 years ago

  • Target version changed from Arvados Future Sprints to 2014-10-29 sprint
Actions
Copy link
 #5

Updated by Peter Amstutz over 9 years ago

  • Assigned To set to Peter Amstutz
Actions
Copy link
 #6

Updated by Peter Amstutz over 9 years ago

  • Status changed from New to In Progress
Actions
Copy link
 #7

Updated by Brett Smith over 9 years ago

5716ec8 is good to merge, thanks.

Actions
Copy link
 #8

Updated by Anonymous over 9 years ago

  • Status changed from In Progress to Resolved

Applied in changeset arvados|commit:269adb302bf244332706a1fe053feddc402eb4be.

Actions
Copy link
 #9

Updated by Brett Smith over 9 years ago

  • Status changed from Resolved to New
  • Target version changed from 2014-10-29 sprint to Bug Triage

This needs another look. This logic should've detected qr1hi-d1hrv-i1d1jffl9nd5ylv, but apparently didn't—right now the pipeline is active and there's nothing in the log.

Actions
Copy link
 #10

Updated by Ward Vandewege over 9 years ago

  • Target version changed from Bug Triage to Arvados Future Sprints
Actions
Copy link
 #11

Updated by Tom Clegg over 9 years ago

  • Target version changed from Arvados Future Sprints to 2014-12-10 sprint
Actions
Copy link
 #12

Updated by Peter Amstutz over 9 years ago

API's Gemfile.lock arvados-cli (0.1.20141014201516) version pin predates the fix by three days, so the reason the problem appeared is that the api server is still using the old version of arv-run-pipeline-instance.

Actions
Copy link
 #13

Updated by Tom Clegg over 9 years ago

  • Status changed from New to Feedback
Actions
Copy link
 #14

Updated by Peter Amstutz over 9 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: Atom PDF