Actions
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:
Category:
Crunch
Target version:
Story points:
0.5
Related issues
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
Updated by Peter Amstutz over 9 years ago
- Target version set to Arvados Future Sprints
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
Updated by Ward Vandewege over 9 years ago
- Target version changed from Arvados Future Sprints to 2014-10-29 sprint
Updated by Peter Amstutz over 9 years ago
- Status changed from New to In Progress
Updated by Anonymous over 9 years ago
- Status changed from In Progress to Resolved
Applied in changeset arvados|commit:269adb302bf244332706a1fe053feddc402eb4be.
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.
Updated by Ward Vandewege over 9 years ago
- Target version changed from Bug Triage to Arvados Future Sprints
Updated by Tom Clegg over 9 years ago
- Target version changed from Arvados Future Sprints to 2014-12-10 sprint
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.
Updated by Peter Amstutz over 9 years ago
- Status changed from Feedback to Resolved
Actions