We did the update yesterday and no need to pause. All went well.

*Jason L. Simms, Ph.D., M.P.H.*
Research Computing Manager
Swarthmore College
Information Technology Services
(610) 328-8102


On Thu, Feb 12, 2026 at 12:52 PM Timony, Mick via slurm-users <
[email protected]> wrote:

> Hi All,
>
> If I am not updated the munge key is it possible to install a newer munge
> package without pausing the cluster (marking partitions as down and
> suspending jobs)?
>
> I am concerned about job failures, especially on GPU nodes if I need to
> pause jobs.
>
>
> Thanks
>
> --
> Mick Timony
> Senior DevOps Engineer
> LASER, Longwood, & O2 Cluster Admin
> Harvard Medical School
> --
> ------------------------------
> *From:* william--- via slurm-users <[email protected]>
> *Sent:* Wednesday, February 11, 2026 12:38 PM
> *To:* 'Laura Hild' <[email protected]>
> *Cc:* 'slurm-users' <[email protected]>
> *Subject:* [slurm-users] Re: MUNGE security issue (CVE-2026-25506)
>
> There are quite a few differences in the spec file for 0.5.16 (which does
> build on CentOS 7) and 0.5.18 (which does not).
>
> 0.5.16 spec file does say that it supports  7.9.2009, and the 0.5.18 does
> not.
>
> A key difference is that the older spec file has:
>         BuildRequires:        %{?el7:systemd}%{!?el7:systemd-rpm-macros}
> And the new:
>         BuildRequires:        systemd-rpm-macros
>
> That is enough to cause the rpmbuild to fail.
>
> I have found that just by editing that one line in the spec file to go
> back to the version from 0.5.16, it builds OK on our CentOS 7.9.2009.
> However it fails to install:
>
> # rpm -Uvh /home/apps/slurm/munge/munge-0.5.18-1.el7.x86_64.rpm
> /home/apps/slurm/munge/munge-libs-0.5.18-1.el7.x86_64.rpm
> error: Failed dependencies:
>         /usr/bin/systemd-sysusers is needed by munge-0.5.18-1.el7.x86_64
>         munge-libs(x86-64) = 0.5.13-1.el7 is needed by (installed)
> munge-devel-0.5.13-1.el7.x86_64
>
> A bit of reading shows that system-sysusers does not exist for CentOS 7.
> So if I read it correctly your suggestion is to use the spec file from
> 0.5.16 and edit these lines:
>
> < Version:      0.5.16
> ---
> > Version:      0.5.18
>
> < %{_libdir}/libmunge.so.2.0.0
> ---
> > %{_libdir}/libmunge.so.2.0.1
>
> I tried that and it failed to find a file:
> install: cannot stat 'src/etc/munge.tmpfiles.conf': No such file or
> directory
>
> This file is created in 0.5.16 but not in 0.5.18.
>
> Overall I am curious how some people have been able to build it when there
> do seem to be multiple issues.
>
> William
>
> -----Original Message-----
> From: Laura Hild <[email protected]>
> Sent: 11 February 2026 14:10
> To: [email protected]; [email protected] <
> [email protected]>
> Cc: slurm-users <[email protected]>
> Subject: Re: [slurm-users] Re: MUNGE security issue (CVE-2026-25506)
>
> > In passing, this does not work on CentOS 7 (don't ask...)
>
> How old of CentOS 7?  I know someone who couldn't compile it on 7.4 but
> could compile it on 7.7 and then run it on 7.4.  This was using the Fedora
> specfile, with the Version bumped and the libmunge.so.2.0.0 %file changed
> to .2.0.1.  🤷‍♀️
>
>
>
>
>
> --
> slurm-users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
> --
> slurm-users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
-- 
slurm-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to