Thank you for your reply. You're correct, the systemd commands aren't invoked, however upgrading the slurm rpm effectively pulls the rug from under /usr/sbin/slurmctld. The v17.02 slurm rpm provides /usr/sbin/slurmctld, but from v17.11 that executable is provided by the slurm-slurmctld rpm.
In other words, doing a minimal install of just the slurm and the slurmdbd rpms deletes the slurmctld executable. I haven't explicitly tested this, however I tested the upgrade on a compute node and experimented with the slurmd -- the logic should be the same. I guess that the question that comes to mind is.. Is it a really big deal if the slurmctld process is down whilst the slurmdbd is being upgraded? Bearing in mind that I will probably opt to suspend all run jobs and stop the partitions during the upgrade. Best regards, David ________________________________ From: slurm-users <slurm-users-boun...@lists.schedmd.com> on behalf of Chris Samuel <ch...@csamuel.org> Sent: 26 September 2018 11:26 To: slurm-users@lists.schedmd.com Subject: Re: [slurm-users] Upgrading a slurm on a cluster, 17.02 --> 18.08 On Tuesday, 25 September 2018 11:54:31 PM AEST Baker D. J. wrote: > That will certainly work, however the slurmctld (or in the case of my test > node, the slurmd) will be killed. The logic is that at v17.02 the slurm rpm > provides slurmctld and slurmd. So upgrading that rpm will destroy/kill the > existing slurmctld or slurmd processes. If you do that with the --noscripts then will it really kill the process? Nothing should invoke the systemd commands with that, should it? Or do you mean taking the libraries, etc, away out underneath of the running process will cause it to crash? Might be worth testing that on on a VM to see if it will happen. Best of luck! Chris -- Chris Samuel : https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.csamuel.org%2F&data=01%7C01%7Cd.j.baker%40soton.ac.uk%7C8b7cb9ecbbfe4644d3fa08d6239b7821%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=hdM3hZuFetDEqdCYj4VCrgCZ8hOC2FGsBuS8Ql74Ly0%3D&reserved=0 : Melbourne, VIC
