Are you using Torque or Slurm? If you are using any other adapter but Torque you should convert the value of the “native” key in the submit.yml.erb to an array.
All of the adapters support specifying an array of “native” command line arguments you would pass to the submit command (whether that be sbatch or qsub or bsub etc.). You would replace spaces with commas and put quotes around each argument (i.e.
native: [ "-d", "after:1234.myjob"])
Only the Torque adapter also supports a hash - this difference goes back to a time when we only had Torque (since thats what we currently use at OSC) and had an adapter using the C library.
I might need to call this out in the documentation. If what I’m suggesting is the problem, would adding a warning to https://osc.github.io/ood-documentation/master/install-ihpc-apps.html be helpful. Or better yet, just update OSC’s apps to use the array-style arguments so that they work.
Long term we need to add a sensible abstraction to specifying resources like nodes and cores when we submit a job - then we could drop using “native” in these apps and the OSC specific ones would become more generic.