Hi Jeff, thanks for that lightning-speed reply to Chris!
Could I beg you verify: we want to target submit.yml.erb not script.yml.erb, right?
# So we'd modify:
# rather than:
And the contents of submit.yml.erb should resemble this:
$ cat /var/www/ood/apps/sys/myjobs/submit.yml.erb
Is that correct?
And to be fully explicit, we are not modifying
Sadly, if all of the above is correct, we seemingly still are not successfully copying-over the environment.
To expand slightly on Chris’ inquiry and provide context to future forumdwellers: we’re trying to fix our setup to allow users to use per-line
srun someCommand syntax in batch jobs submitted to Slurm via the Job Composer App. This is probably best explained with some examples:
This job will succeed:
This job will also succeed:
srun --export=all hostname
But this job will fail:
…with output suggesting the environment is bone dry:
slurmstepd: error: execve(): hostname: No such file or directory
srun: error: cn69: task 0: Exited with exit code 2
My understanding of srun’s functionality inside sbatch scripts is that while technically optional, it allows us to collect more metadata on the job.
If relevant, this seems to be similar or the same as our former EL6/OOD 1.6 situation where we’d previously patched the ruby directly to regain “srun functionality”.
Thanks for your assistance!