On 29-09-2023 17:33, Ryan Novosielski wrote:
I’ll just say, we haven’t done an online/jobs running upgrade recently
(in part because we know our database upgrade will take a long time, and
we have some processes that rely on -M), but we have done it and it does
work fine. So the paranoia isn’t
: Friday, September 29, 2023 11:33 AM
To: Slurm User Community List
Subject: Re: [slurm-users] Steps to upgrade slurm for a patchlevel change?
You don't often get email from novos...@rutgers.edu. Learn why this is
important<https://aka.ms/LearnAboutSenderIdentification>
I’ll just say, we haven’
gt;
on behalf of Ryan Novosielski
<mailto:novos...@rutgers.edu>
Sent: Friday, September 29, 2023 2:48 AM
To: Slurm User Community List
<mailto:slurm-users@lists.schedmd.com>
Subject: Re: [slurm-users] Steps to upgrade slurm for a patchlevel change?
You don't often get email from
*Subject:* Re: [slurm-users] Steps to upgrade slurm for a patchlevel
change?
You don't often get email from novos...@rutgers.edu. Learn why this is
important <https://aka.ms/LearnAboutSenderIdentification>
I started off writing there’s really no particular process for
unity List
Subject: Re: [slurm-users] Steps to upgrade slurm for a patchlevel change?
You don't often get email from novos...@rutgers.edu. Learn why this is
important<https://aka.ms/LearnAboutSenderIdentification>
I started off writing there’s really no particular process for these/just
I started off writing there’s really no particular process for these/just do
your changes and start the new software (be mindful of any PATH that might
contain data that’s under your software tree, if you have that setup), and that
you might need to watch the timeouts, but I figured I’d have a
On 9/28/23 17:58, Groner, Rob wrote:
There's 14 steps to upgrading slurm listed on their website, including
shutting down and backing up the database. So far we've only updated
slurm during a downtime, and it's been a major version change, so we've
taken all the steps indicated.
We now want
A colleague of mine has it scripted out quite well, so I can't speak to
*all* of the details. However, we have a user that we submit our jobs as
and it does the steps for upgrading (yum, dnf, etc). The jobs are
wholenode/exclusive so nothing else can run there, and then a few other
steps might be
There's 14 steps to upgrading slurm listed on their website, including shutting
down and backing up the database. So far we've only updated slurm during a
downtime, and it's been a major version change, so we've taken all the steps
indicated.
We now want to upgrade from 23.02.4 to 23.02.5.
