Arvados

When arv-run-pipeline-instance submits a component as a job, and the job submission is rejected by API server, the error is not recorded (and thus not reported to the user in Workbench) and the pipeline simply fails with no explanation.

Example case:

I went to run a job which had an invalid commit hash in "minimum_script_version". This fails (reported in bug #3124) with the following error, but the user can't debug why the job failed without access to the crunch-dispatch logs.

2014-06-30_15:02:13.08383 arv-run-pipeline-instance 4399: create job: ["#<ArgumentError: Invalid operand type 'NilClass' fo
r 'in' operator in filters>"] with attributes {:script=>"run-command", :script_parameters=>{:command=>["java", "-Xmx8g", "-
jar", "$(dir $(picard))/CreateSequenceDictionary.jar", "R=$(file $(fasta))", "O=$(basename $(fasta)).dict"], :fasta=>"27793
0109b2dfec9412d489332784605+2009/human_g1k_v37.fasta", :picard=>"88447c464574ad7f79e551070043f9a9+1970"}, :script_version=>
"master", :repository=>"arvados", :nondeterministic=>nil, :output_is_persistent=>false, :runtime_constraints=>{:docker_imag
e=>"arvados/jobs-bwa-samtools"}, :owner_uuid=>"4xphq-tpzed-d6gnynp5uioqnxo", :minimum_script_version=>"96023b1eb656979a4e0e
87f80818f23d23511c1e", :exclude_script_versions=>nil, :no_reuse=>nil}