Ticket 9104 - pam_slurm_adopt locks out logins on bad slurm.conf
Summary: pam_slurm_adopt locks out logins on bad slurm.conf
Status: RESOLVED INVALID
Alias: None
Product: Slurm
Classification: Unclassified
Component: Other (show other tickets)
Version: 20.02.2
Hardware: Linux Linux
: 6 - No support contract
Assignee: Jacob Jenson
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2020-05-22 10:54 MDT by adam.tygart
Modified: 2020-05-22 10:54 MDT (History)
0 users

See Also:
Site: -Other-
Slinky Site: ---
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
Google sites: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ---
NoveTech Sites: ---
Nvidia HWinf-CS Sites: ---
OCF Sites: ---
Recursion Pharma Sites: ---
SFW Sites: ---
SNIC sites: ---
Tzag Elita Sites: ---
Linux Distro: ---
Machine Name:
CLE Version:
Version Fixed:
Target Release: ---
DevPrio: ---
Emory-Cloud Sites: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this ticket.
Description adam.tygart 2020-05-22 10:54:08 MDT 
If a bad slurm.conf exists, for instance either for a different version of slurm or being unable to be look up the SlurmUser, pam_slurm_adopt issues 'fatal: Unable to process configuration file' and will not allow the user to login, even as root.

In these events I would expect that the action_generic_failure action would be taken. This doesn't seem to happen.

This is likely related to the fixes applied for #8692