Closed hoba87 closed 1 year ago
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:
You may have figured this out at this point, but even though you seem to be running the service as root, the calls to slurm are probably being done through sudo which may have a secure path and that path may not include your slurm installation. So I'd look at your /etc/sudoers
file and likely set the secure_path.
That was indeed the case. Adjusting the secure_path solves this for me.
Bug description
Without specifying the full path to the slurm executables like sbatch in batchspawner.py, these are not found. I have added the slurm bin directory to the jupyterhub service environment.
Expected behaviour
JupyterHub uses its environment to find slurm executables.
Actual behaviour
Full paths to slurm executables are needed
How to reproduce
Your personal set up
CentOS 8.2 python 3.7.9 jupyterhub 1.4.0 batchspawner 1.1.1
Configuration