Ticket 13054

Summary:	Test option to "scontrol reconfig" after updating the configuration file
Product:	Slurm	Reporter:	Mallick Arigapudi <mallick.arigapudi>
Component:	Configuration	Assignee:	Jason Booth <jbooth>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	3 - Medium Impact
Priority:	---	CC:	marshall
Version:	21.08.4
Hardware:	Linux
OS:	Linux
Site:	Intel CRT	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:	---

Description Mallick Arigapudi 2021-12-16 11:02:06 MST

I made some changes/updates to /etc/slurm.conf file. Obviously unknowingly I made some mistakes with the syntax or typos.
Now when I run 
# scontrol reconfig
is failing, bringing slurm to a stand still. Until the error is fixed, I am pushed to the wall by hundreds of users.

Is there a test option before I run the above command to check if my updates to the configuration file are correct/good enough?
This option will save us lots of time with no disruption to the ops.

Comment 4 Jason Booth 2021-12-16 13:03:12 MST

We have a number of bugs surrounding this type of request, however we do not have anything on the roadmap at this time to add this type of feature (bug#3445, bug#2538, and bug#10597).

At this time, you could run a Slurm client command with the updated slurm.conf *before* running scontrol reconfigure. The client command reads slurm.conf and should fail if slurm.conf is invalid.

For now, I am resolving this out as a duplicate.

*** This ticket has been marked as a duplicate of ticket 10597 ***