<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I think it should be, but you should be able to run a test and
find out.</p>
<p>-Paul Edmon-<br>
</p>
<div class="moz-cite-prefix">On 5/17/22 12:13 PM, byron wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJ+YQypXpqJ5aV74da-AR21MhyDT4LF3HAwrDv_069wJxg1DeA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Sorry, I should have been clearer. I understand that with
regards to slurmd / slurmctld you can skip a major release
without impacting running jobs etc. My questions was about
upgrading slurmdbd and whether it was necessary to upgrade
through the intermediate major releases (which I know
understand is necessary).</div>
<div><br>
</div>
<div>Thanks<br>
</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, May 17, 2022 at 4:49
PM Paul Edmon <<a href="mailto:pedmon@cfa.harvard.edu"
moz-do-not-send="true" class="moz-txt-link-freetext">pedmon@cfa.harvard.edu</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>The slurm docs say you can do two major releases at a
time (<a
href="https://slurm.schedmd.com/quickstart_admin.html"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://slurm.schedmd.com/quickstart_admin.html</a>):</p>
<p>"Almost every new major release of Slurm (e.g. 20.02.x to
20.11.x) involves changes to the state files with new data
structures, new options, etc. Slurm permits upgrades to a
new major release from the past two major releases, which
happen every nine months (e.g. 20.02.x or 20.11.x to
21.08.x) without loss of jobs or other state information."</p>
<p>As for old versions of slurm I think at this point you
would need to contact SchedMD. I'm sure they have past
releases they can hand out if you are bootstrapping to a
newer release.</p>
<p>-Paul Edmon-<br>
</p>
<div>On 5/17/22 11:42 AM, byron wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Thanks Brian for the speedy responce.<br>
</div>
<div><br>
</div>
<div>Am I not correct in thinking that if I just go from
19.05 to 20.11 then there is the advantage that I can
upgrade slurmd and slurmctld in one go and it won't
affect the running jobs since upgrading to a new major
release from the past two major releases doesn't
affect the state information. Or are you saying that
in this case (19.05 direct to 21.08) there isn't any
impact to running jobs either. Or did you step
through all the versions when upgrading slurmd and
slurmctld also?</div>
<div><br>
</div>
<div>Also where do I get a copy of 20.2 from if schedMD
aren't providing it as a download.</div>
<div><br>
</div>
<div>Thanks<br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, May 17, 2022
at 4:05 PM Brian Andrus <<a
href="mailto:toomuchit@gmail.com" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">toomuchit@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px
0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">You need to step
upgrade through major versions (not minor).<br>
<br>
So 19.05=>20.x<br>
<br>
I would highly recommend going to 21.08 while you are
at it.<br>
I just did the same migration (although they started
at 18.x) with no <br>
issues. Running jobs were not impacted and users
didn't even notice.<br>
<br>
Brian Andrus<br>
<br>
<br>
On 5/17/2022 7:35 AM, byron wrote:<br>
> Hi<br>
><br>
> I'm looking at upgrading our install of slurm
from 19.05 to 20.11 in <br>
> responce to the recenty announced security
vulnerabilities.<br>
><br>
> I've been through the documentation / forums and
have managed to find <br>
> the answers to most of my questions but am still
unclear about the <br>
> following<br>
><br>
> - In upgrading the slurmdbd from 19.05 to 20.11
do I need to go <br>
> through all the versions (19.05 => 20.2 =>
20.11)? From reading the <br>
> forums it look as though it is necesary<br>
> <a
href="https://groups.google.com/g/slurm-users/c/fftVPaHvTzQ/m/YTWo1mRjAwAJ"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://groups.google.com/g/slurm-users/c/fftVPaHvTzQ/m/YTWo1mRjAwAJ</a><br>
> <a
href="https://groups.google.com/g/slurm-users/c/kXtepX8-L7I/m/udwySA3bBQAJ"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://groups.google.com/g/slurm-users/c/kXtepX8-L7I/m/udwySA3bBQAJ</a><br>
> However if that is the case it would seem
strange that SchedMD have <br>
> removed 20.2 from the downloads page (I
understand the reason is that <br>
> it contains the exploit) if it is still required
for the upgrade.<br>
><br>
> - We are running version 5.5.68 of the MariaDB,
the version that comes <br>
> with centos7.9. I've seen a few references to
upgrading v5.5 but <br>
> they were in the context of upgrading from slurm
17 to 18. I'm <br>
> wondering if its ok to stick with this version
since we're already on <br>
> slurm 19.05.<br>
><br>
> Any help much appreciated.<br>
><br>
><br>
><br>
><br>
<br>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</body>
</html>