Bug #3978

[SDKs] Pipelines started from the CLI should set status to "Paused" when aborted

Added by Abram Connelly almost 5 years ago. Updated almost 5 years ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
SDKs
Target version:
Start date:
09/24/2014
Due date:
% Done:

0%

Estimated time:
(Total: 0.00 h)
Story points:
1.0

Description

Pipelines that have been stopped or will never be run show up in the 'Active pipelines' panel from the Dashboard. For me, these appear because I run pipelines from the comand line and they occasionally stop midway through the pipeline (sometimes due to bugs, sometimes because I stop them myself, etc.). These are pipelines I probably will not run again or have long forgotten, but they clutter the 'Active pipelines' section. They should be put in another section, perhaps the 'Recently finished' panel or some other section in case I want to refer back to them later.

Fix (at least partial):
  • arv-run-pipeline-instance should set the pipeline instance status to "Paused" when an uncaught exception is thrown (possibly including ctrl-C)
  • Make sure paused pipelines don't show up in the "active" list on dashboard

Subtasks

Task #4212: [Workbench] Pipeline instance viewer should not omit paused pipelinesNew

Task #4211: a-r-p-i sets pipeline instance to 'Paused' in a catchall exceptionNew

History

#1 Updated by Tim Pierce almost 5 years ago

Check with Tom on intended behavior here.

#2 Updated by Ward Vandewege almost 5 years ago

  • Subject changed from Stale pipelines appear in 'recently finished piplines' panel to [Workbench] Stale pipelines appear in 'recently finished pipelines' panel

#3 Updated by Tom Clegg almost 5 years ago

Let's start by updating state to Stopped in a-r-p-i before exiting -- at least in the cases where that's possible. (We can't help with SIGKILL, but at least SIGINT should clean up.)

#4 Updated by Tim Pierce almost 5 years ago

  • Description updated (diff)
  • Target version changed from Bug Triage to Arvados Future Sprints
  • Story points set to 1.0

#5 Updated by Tim Pierce almost 5 years ago

  • Subject changed from [Workbench] Stale pipelines appear in 'recently finished pipelines' panel to [SDK] Pipelines started from the CLI set status to "Stopped" when aborted
  • Category set to SDKs

#6 Updated by Ward Vandewege almost 5 years ago

  • Target version changed from Arvados Future Sprints to 2014-10-29 sprint

#7 Updated by Tom Clegg almost 5 years ago

  • Subject changed from [SDK] Pipelines started from the CLI set status to "Stopped" when aborted to [SDKs] Pipelines started from the CLI should set status to "Stopped" when aborted

#8 Updated by Tim Pierce almost 5 years ago

  • Assigned To set to Tim Pierce

#9 Updated by Tom Clegg almost 5 years ago

  • Subject changed from [SDKs] Pipelines started from the CLI should set status to "Stopped" when aborted to [SDKs] Pipelines started from the CLI should set status to "Paused" when aborted
  • Description updated (diff)

#10 Updated by Tim Pierce almost 5 years ago

This looks like 8dea7244cf5e50b9fa70bec15b1db3fd2cdd03bf should have already implemented this.

If it is still not working as intended, we should identify a repeatable case and find out why aborted pipelines are not getting set to "Paused" as intended.

#11 Updated by Tim Pierce almost 5 years ago

  • Target version changed from 2014-10-29 sprint to Arvados Future Sprints

#12 Updated by Tom Clegg almost 5 years ago

  • Assigned To deleted (Tim Pierce)

Also available in: Atom PDF