Bug #5906
Updated by Brett Smith almost 9 years ago
h2. Development story
If you build a pipeline that refers to a remote repository that cannot be fetched (e.g., typo in the URL), the pipeline will appear to "hang." Nothing will run, and the pipeline state will not change.
crunch-dispatch should detect this error case, mark the job failed, and report the error in such a way that the user can see it in Workbench's log tabs for the job and the parent pipeline (if any).
h2. Original bug report
Pipeline su92l-d1hrv-6lv8np1xul1fcaf looks to have hung indefinitely. It looks like the cause of it is a bad 'repository' parameter. Here is the relevant section:
<pre>
...
"script": "run-command",
"script_version": "master",
"repository": "https://git.curoverse.com/get-evidence-arvados-scripts",
...
</pre>
Trying to issue a @git clone@ command on the above repository causes it to hang for 60 seconds and then fail:
<pre>
$ git clone https://git.curoverse.com/get-evidence-arvados-scripts
Cloning into 'get-evidence-arvados-scripts'...
fatal: unable to access 'https://git.curoverse.com/get-evidence-arvados-scripts/': Failed to connect to git.curoverse.com port 443: Connection timed out
</pre>
As of this writing, the pipeline has been queued for over 16 hours. Also as of this writing, the queue count from the dashboard indicates 0 pipelines queued. There is one 'busy' node that looks to be processing another active pipeline. Screenshot attached.