Summary: | slurmctld should start after nss-user-lookup.target | ||
---|---|---|---|
Product: | Slurm | Reporter: | Yu Watanabe <watanabe.yu> |
Component: | slurmctld | Assignee: | Jacob Jenson <jacob> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | 6 - No support contract | ||
Priority: | --- | CC: | Ole.H.Nielsen, watanabe.yu |
Version: | 16.05.x | ||
Hardware: | Linux | ||
OS: | Linux | ||
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: | --- |
Description
Yu Watanabe
2016-04-13 16:38:23 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? munge.service has already been added to version 17.02 |