Ticket 14562

Summary: slurmd fails to start
Product: Slurm Reporter: Sudhakar Lakkaraju <slakkaraju>
Component: slurmdAssignee: Nate Rini <nate>
Status: RESOLVED INFOGIVEN QA Contact:
Severity: 4 - Minor Issue    
Priority: --- CC: nate
Version: 22.05.0   
Hardware: Linux   
OS: Linux   
Site: ASC 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: ---
Attachments: slurm.conf
cgroup.conf

Description Sudhakar Lakkaraju 2022-07-18 14:51:35 MDT 
Created attachment 25904 [details]
slurm.conf

Hi,
We are in the process of testing slurm 22.05 version on our test nodes.
slurmctld starts fine, but slurmd fails to start.

Here are the error messages:

slurmd -Dvvvvv
slurmd: error: _parse_next_key: Parsing error at unrecognized key: TaskAffinity
slurmd: fatal: Could not open/read/parse cgroup.conf file /etc/slurm/cgroup.conf
Comment 1 Sudhakar Lakkaraju 2022-07-18 14:52:18 MDT 
Created attachment 25905 [details]
cgroup.conf
Comment 2 Nate Rini 2022-07-18 14:53:14 MDT 
Remove the line with TaskAffinity in /etc/slurm/cgroup.conf. That feature was removed.
Comment 3 Sudhakar Lakkaraju 2022-07-19 07:43:56 MDT 
Thank you.
Issue resolved. Please close the ticket.


On Jul 18, 2022, at 3:53 PM, bugs@schedmd.com<mailto:bugs@schedmd.com> wrote:

Nate Rini<mailto:nate@schedmd.com> changed bug 14562<https://bugs.schedmd.com/show_bug.cgi?id=14562>
What    Removed Added
CC              nate@schedmd.com<mailto:nate@schedmd.com>

Comment # 2<https://bugs.schedmd.com/show_bug.cgi?id=14562#c2> on bug 14562<https://bugs.schedmd.com/show_bug.cgi?id=14562> from Nate Rini<mailto:nate@schedmd.com>

Remove the line with TaskAffinity in /etc/slurm/cgroup.conf. That feature was
removed.

________________________________
You are receiving this mail because:

  *   You reported the bug.
Comment 4 Nate Rini 2022-07-19 08:32:35 MDT 
Please make sure to read the RELEASE_NOTES before upgrading next time. Breaking changes such as this one are listed there.

Closing out ticket per your reply.