Bug #3974
closed
[SDKs] CLI 'arv pipeline run --run-pipeline-here' should change instance state from 'ready' (or 'not running'?) to 'RunningOnClient'
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.
Files
Related issues
Updated by Tim Pierce over 9 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?
Updated by Tim Pierce over 9 years ago
- Target version changed from Bug Triage to Arvados Future Sprints
Updated by Tom Clegg over 9 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"?)
Updated by Tom Clegg over 9 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'
Updated by Ward Vandewege almost 3 years ago
- Target version deleted (
Arvados Future Sprints)
Updated by 
