As mentioned on the mailing list, this breaks essentially all OpenMPI releases on Slurm 19.05: https://groups.google.com/d/msg/slurm-users/A0mKkveOT08/eM6bruJiBAAJ
Yes, please.
+1 to revert this change.
+1 -k
This will impact our site as well. What was the rationale behind this decision?
Created attachment 10536 [details] Add --cpu_bind as an alias for --cpu-bind. The attached patch adds --cpu_bind back in as an alias of --cpu-bind for salloc/sbatch/srun. Some variant of this patch - albeit with a warning message added in to note that --cpu-bind is the correct spelling - will be in 19.05.1 when released, and supported through the 19.05 release cycle. As a few people have noted on the mailing list, we do encourage sites to use srun - ideally with PMI2 or PMIx - instead of mpiexec/mpirun, but we will work with OpenMPI to get this updated in their wrapper scripting. - Tim
As noted on the mailing list, this is already fixed in OpenMPI's master branch. Hopefully it can get backported and new releases made. Thanks for the patch -- going to test this out now.
I've added --cpu_bind back in as an alias, this will be included with 19.05.1 when released, and is functionally identical to the patch attached here. commit d5cf91857e2c14ebd7c70c2eb2d71af43945a297 Author: Tim Wickberg <tim@schedmd.com> AuthorDate: Tue Jul 9 13:08:53 2019 -0600 srun - restore --cpu_bind as an alias for --cpu-bind. Needed to maintain compatibility with OpenMPI's mpirun/mpiexec launch commands. Bug 7191.