Ticket 9104

Summary: pam_slurm_adopt locks out logins on bad slurm.conf
Product: Slurm Reporter: adam.tygart
Component: OtherAssignee: Jacob Jenson <jacob>
Status: RESOLVED INVALID QA Contact:
Severity: 6 - No support contract    
Priority: ---    
Version: 20.02.2   
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: Target Release: ---
DevPrio: --- Emory-Cloud Sites: ---

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