Bug #3974

[SDKs] CLI 'arv pipeline run --run-pipeline-here' should change instance state from 'ready' (or 'not running'?) to 'RunningOnClient'

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

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

0%

Estimated time:
Story points:
0.5

Description

I started the pipeline instance 9tee4-d1hrv-0r1d0v2q7j2ym9p from my 9tee4 VM, issuing the following command:

...
arv pipeline run --run-pipeline-here --instance $ARVUUID $opt

(where '$opt' has a few parameters filled in, i.e. ChopGFF:CYTOBAND=...).

From the workbench page on 9tee4, I see the status of the pipeline template as 'not running', even though the pipeline is running (from the command line on my VM) and the relevant job from that pipeline is executing (and appears in workbench).

Screenshots attached showing the workbench state.

pipeline_not_running.jpg (54.6 KB) pipeline_not_running.jpg showing the pipeline not running Abram Connelly, 09/24/2014 03:30 PM
job_running.jpg (80.4 KB) job_running.jpg showing the active job in the pipeline Abram Connelly, 09/24/2014 03:31 PM

Related issues

Related to Arvados - Bug #3834: [Workbench] pipeline instance that is RunningOnClient should be rendered as Running, not Ready.New09/08/2014

History

#1 Updated by Tim Pierce almost 5 years ago

discuss with Peter and Tom: what's the desired behavior here? Should API server recognize the pipeline status as "running" if it is not being managed by crunch-dispatch, and if not, how do we communicate that to the user?

#2 Updated by Tim Pierce almost 5 years ago

  • Target version changed from Bug Triage to Arvados Future Sprints

#3 Updated by Tom Clegg almost 5 years ago

Tim Pierce wrote:

discuss with Peter and Tom: what's the desired behavior here? Should API server recognize the pipeline status as "running" if it is not being managed by crunch-dispatch, and if not, how do we communicate that to the user?

State should be RunningOnClient. Workbench should render as running, with some way to tell the difference between OnClient and OnServer. (Perhaps "Running" / "Running in user terminal session"?)

#4 Updated by Tom Clegg almost 5 years ago

  • Subject changed from CLI 'arv pipeline run --run-pipeline-here' does not update the state from 'ready' (or 'not running'?) to 'run' to [SDKs] CLI 'arv pipeline run --run-pipeline-here' should change instance state from 'ready' (or 'not running'?) to 'RunningOnClient'

#5 Updated by Tom Clegg almost 5 years ago

  • Story points set to 0.5

Also available in: Atom PDF