CentOS 7: update slurm - problems

[mbkuz]

yum update slurm
gives for my CentOS 7.9.2009-based distributive (kernel 3.10.0-1160.11.1) interdependence problems (conflicts) after confirming the installation:
...
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Updating:
slurm x86_64 20.11.2-2.el7 epel 1.7 M
Installing for dependencies:
hdf5 x86_64 1.8.12-11.el7 epel 1.6 M
libaec x86_64 1.0.4-1.el7 epel 34 k
pmix x86_64 1.1.3-1.el7 epel 114 k

Transaction Summary
================================================================================
Install ( 3 Dependent packages)
Upgrade 1 Package
...

Transaction check error:
file /usr/lib64/slurm/accounting_storage_none.so from install of slurm-20.11.2-2.el7.x86_64 conflicts with file from package slurm-plugins-16.05.5-1.el7.centos.x86_64
... (etc with slurm-plugins)
file /usr/lib64/slurm/accounting_storage_mysql.so from install of slurm-20.11.2-2.el7.x86_64 conflicts with file from package slurm-sql-16.05.5-1.el7.centos.x86_64
file /usr/lib64/slurm/jobcomp_mysql.so from install of slurm-20.11.2-2.el7.x86_64 conflicts with file from package slurm-sql-16.05.5-1.el7.centos.x86_64
file /usr/lib64/slurm/job_submit_pbs.so from install of slurm-20.11.2-2.el7.x86_64 conflicts with file from package slurm-torque-16.05.5-1.el7.centos.x86_64
file /usr/lib64/slurm/auth_munge.so from install of slurm-20.11.2-2.el7.x86_64 conflicts with file from package slurm-munge-16.05.5-1.el7.centos.x86_64

Yum update slurm-devel, slurm-slurmdbd, slurm-torque gives similar problems. Is this a temporary error or should I work around this problem - then how?

[TrevorH]

Try yum update slurm\*

If that doesn't work then I suggest reporting the problem to the EPEL maintainer.

[mbkuz]

Yes - I have of course tried yum update slurm- * and it gives the same problem.

[chemal]

The slurm package in epel is new. What you already have is not from epel and packaged differently.

[jlehtone]

The slurm package in epel is new. What you already have is not from epel and packaged differently.

This. I was shocked by this thread, because it revealed that slurm has been added to EPEL (this month).
Slurm is something that I would not let update automatically. Thanks for the heads up.

There is more. Slurm-20.11.2 to slurm-16.05.5 is a huge jump in versions. The syntax of slurm config has changed.

https://slurm.schedmd.com/quickstart_admin.html writes:
"Slurm daemons will support RPCs and state files from the two previous major releases (e.g. a version 20.11.x SlurmDBD will support slurmctld daemons and commands with a version of 20.11.x, 20.02.x, or 19.05.x). This means that upgrading at least once each year is recommended. Otherwise, intermediate upgrades will be required to preserve state information."

In other words, direct "live update" is not possible. To keep state you would have to do something like 16.05 => 17.02 => 18.08 => 20.02 => 20.11.

Finally,
https://www.schedmd.com/archives.php writes:
Due to a security vulnerability (CVE-2018-10995), all versions of Slurm prior to 17.02.11 or 17.11.7 are no longer available for download.

Your current slurm is vulnerable and must be updated.

[mbkuz]

Thanks !!
But if the queue is free now, may I simple to do:
yum remove slurm*
and then
yum install slurm
?

[jlehtone]

Probably. You will essentially create a new slurm cluster (and config for it).

Do you have the accounting database and want to keep it? Not sure whether schema can update.