Indeed I had misunderstood you, I thought that you were applying Slurm point upgrades automatically. I think that the reason for that misunderstanding is that we use Foreman & Katello for our patching and for all our Slurm nodes (on, I think 25.04) are flagged as needing an Erratum applied that is Slurm 26.05 or the like, to fix a Slurm security bug. Every time that I do patching (which is not yet automatically scheduled) I have to be careful to de-select that Erratum, and only apply the others. Your process now makes more sense to me. We only have 22 nodes so I can manage a while more with manually draining subsets of the cluster and applying patches. This would be easier if we did not use LUKS-encrypted disks as on every reboot we still have to manually enter the encryption key, but that is quite a different problem. Thanks for clarifying that, and your Slurm Wiki pages have been very useful to me for many years now. William -----Original Message----- From: Ole Holm Nielsen via slurm-users <slurm-users@lists.schedmd.com> Sent: 26 October 2026 13:35 To: slurm-users@lists.schedmd.com Subject: [slurm-users] Re: Making easy and simple security updates of Slurm compute nodes Hi William, On 10/26/26 13:49, william--- via slurm-users wrote:
I have put off applying updates as our Slurm install was built from RPMs we built, selecting the options that we need - as I understand it features are included if the corresponding 'dev' libraries are found on the build system. We used the process documented here https://wiki.fysik.dtu.dk/Niflheim_system/Slurm_installation/#build-sl urm-rpms>>
I'm glad my Slurm Wiki pages have been of use to you :-) I'm unsure what you mean by 'dev' libraries?
We could now use the Rocky Linux 10 RPMs (indeed the Errata keeps offering to do updates) but I have assumed that these would not include or exclude the features in the same way, so if we allowed it to update this would break Slurm. Or is this not so?
Maybe I'm misunderstanding you, but my mail wasn't referring to Slurm updates, but to general RockyLinux (or other EL distributions) where kernel and many other updates are currently coming out daily!
It would of course be desirable to be able to apply at least all security updates promptly after they are released.
This is what we do. My method basically does "dnf upgrade" of all updates on compute nodes in a controlled manner and without disturbing any user jobs. Best regards, Ole -- slurm-users mailing list -- slurm-users@lists.schedmd.com To unsubscribe send an email to slurm-users-leave@lists.schedmd.com