Bug 2637 - slurmctld should start after nss-user-lookup.target
Summary: slurmctld should start after nss-user-lookup.target
Status: RESOLVED FIXED
Alias: None
Product: Slurm
Classification: Unclassified
Component: slurmctld (show other bugs)
Version: 16.05.x
Hardware: Linux Linux
: --- 6 - No support contract
Assignee: Jacob Jenson
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2016-04-13 16:38 MDT by Yu Watanabe
Modified: 2016-10-24 16:45 MDT (History)
2 users (show)

See Also:
Site: -Other-
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ---
OCF Sites: ---
Recursion Pharma Sites: ---
SFW Sites: ---
SNIC sites: ---
Linux Distro: ---
Machine Name:
CLE Version:
Version Fixed: 17.02.0-pre3
Target Release: ---
DevPrio: ---
Emory-Cloud Sites: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yu Watanabe 2016-04-13 16:38:23 MDT
Please add
=====
After=nss-user-lookup.target munge.service
=====
in slurmctld.service systemd unit file.

As described at
https://www.freedesktop.org/software/systemd/man/systemd.special.html#Special%20Passive%20System%20Units
> A target that should be used as synchronization point for 
> all user/group name service lookups. 
> All services for which the availability of the full 
> user/group database is essential should be ordered after this target, 
> but not pull it in. 

The service slurmctld.service require to access full user/group database at boot time. So, it should start after nss-user-lookup.target.

Without this dependency, and if user/group database service (e.g. ypbind) starts after slurmctld, then users given by the database cannot submit jobs correctly.

Also, if we use munge plugins, munge.service should start before that slurmctld starts.
Comment 1 Ole.H.Nielsen@fysik.dtu.dk 2016-10-19 03:39:08 MDT
I agree about the munge.service.  But we don't employ a user/group database service (e.g. ypbind), only local passwd files, so in this case I suppose that the nss-user-lookup.target isn't needed, right?  What's would a more general approach then be?
Comment 2 Moe Jette 2016-10-24 16:45:14 MDT
munge.service has already been added to version 17.02