Slurm versions 24.05.2, 23.11.9, and 23.02.8 are now available and
include a fix for a recently discovered security issue with the switch
plugins.
SchedMD customers were informed on July 17th and provided a patch on
request; this process is documented in our security policy. [1]
For the switch/hpe_slingshot and switch/nvidia_imex plugins, a user
could override the isolation between Slingshot VNIs or IMEX channels.
If you do not have one of these switch plugins configured, then you are
not impacted by this issue.
It is unclear what, if any, information could be accessed with access to
an unauthorized channel. This disclosure is being made out of an
abundance of caution.
If you do have one of these plugins enabled, the slurmctld must be
restarted before the slurmd daemons to avoid disruption.
Downloads are available at https://www.schedmd.com/downloads.php .
Release notes follow below.
- Tim
[1] https://www.schedmd.com/security-policy/
--
Tim Wickberg
Chief Technology Officer, SchedMD LLC
Commercial Slurm Development and Support
> * Changes in Slurm 24.05.2
> ==========================
> -- Fix energy gathering rpc counter underflow in _rpc_acct_gather_energy when
> more than 10 threads try to get energy at the same time. This prevented
> the possibility to get energy from slurmd by any step until slurmd was
> restarted, so losing energy accounting metrics in the node.
> -- accounting_storage/mysql - Fix issue where new user with wckey did not
> have a default wckey sent to the slurmctld.
> -- slurmrestd - Prevent slurmrestd segfault when handling the following
> endpoints when none of the optional parameters are specified:
> 'DELETE /slurm/v0.0.40/jobs'
> 'DELETE /slurm/v0.0.41/jobs'
> 'GET /slurm/v0.0.40/shares'
> 'GET /slurm/v0.0.41/shares'
> 'GET /slurmdb/v0.0.40/instance'
> 'GET /slurmdb/v0.0.41/instance'
> 'GET /slurmdb/v0.0.40/instances'
> 'GET /slurmdb/v0.0.41/instances'
> 'POST /slurm/v0.0.40/job/{job_id}'
> 'POST /slurm/v0.0.41/job/{job_id}'
> -- Fix IPMI energy gathering when no IPMIPowerSensors are specified in
> acct_gather.conf. This situation resulted in an accounted energy of 0
> for job steps.
> -- Fix a minor memory leak in slurmctld when updating a job dependency.
> -- scontrol,squeue - Fix regression that caused incorrect values for
> multisocket nodes at '.jobs[].job_resources.nodes.allocation' for
> 'scontrol show jobs --(json|yaml)' and 'squeue --(json|yaml)'.
> -- slurmrestd - Fix regression that caused incorrect values for
> multisocket nodes at '.jobs[].job_resources.nodes.allocation' to be dumped
> with endpoints:
> 'GET /slurm/v0.0.41/job/{job_id}'
> 'GET /slurm/v0.0.41/jobs'
> -- jobcomp/filetxt - Fix truncation of job record lines > 1024 characters.
> -- Fixed regression that prevented compilation on FreeBSD hosts.
> -- switch/hpe_slingshot - Drain node on failure to delete CXI services.
> -- Fix a performance regression from 23.11.0 in cpu frequency handling when no
> CpuFreqDef is defined.
> -- Fix one-task-per-sharing not working across multiple nodes.
> -- Fix inconsistent number of cpus when creating a reservation using the
> TRESPerNode option.
> -- data_parser/v0.0.40+ - Fix job state parsing which could break filtering.
> -- Prevent cpus-per-task to be modified in jobs where a -c value has been
> explicitly specified and the requested memory constraints implicitly
> increase the number of CPUs to allocate.
> -- slurmrestd - Fix regression where args '-s v0.0.39,dbv0.0.39' and
> '-d v0.0.39' would result in 'GET /openapi/v3' not registering as a valid
> possible query resulting in 404 errors.
> -- slurmrestd - Fix memory leak for dbv0.0.39 jobs query which occurred if the
> query parameters specified account, association, cluster, constraints,
> format, groups, job_name, partition, qos, reason, reservation, state, users,
> or wckey. This affects the following endpoints:
> 'GET /slurmdb/v0.0.39/jobs'
> -- slurmrestd - In the case the slurmdbd does not respond to a persistent
> connection init message, prevent the closed fd from being used, and instead
> emit an error or warning depending on if the connection was required.
> -- Fix 24.05.0 regression that caused the slurmdbd not to send back an error
> message if there is an error initializing a persistent connection.
> -- Reduce latency of forwarded x11 packets.
> -- Add "curr_dependency" (representing the current dependency of the job)
> and "orig_dependency" (representing the original requested dependency of
> the job) fields to the job record in job_submit.lua (for job update) and
> jobcomp.lua.
> -- Fix potential segfault of slurmctld configured with
> SlurmctldParameters=enable_rpc_queue from happening on reconfigure.
> -- Fix potential segfault of slurmctld on its shutdown when rate limitting
> is enabled.
> -- slurmrestd - Fix missing job environment for SLURM_JOB_NAME,
> SLURM_OPEN_MODE, SLURM_JOB_DEPENDENCY, SLURM_PROFILE, SLURM_ACCTG_FREQ,
> SLURM_NETWORK and SLURM_CPU_FREQ_REQ to match sbatch.
> -- Add missing bash-completions dependency to slurm-smd-client debian package.
> -- Fix bash-completions installation in debian pacakges.
> -- Fix GRES environment variable indices being incorrect when only using a
> subset of all GPUs on a node and the --gres-flags=allow-task-sharing option
> -- Add missing mariadb/mysql client package dependency to debian package.
> -- Fail the debian package build early if mysql cannot be found.
> -- Prevent scontrol from segfaulting when requesting scontrol show reservation
> --json or --yaml if there is an error retrieving reservations from the
> slurmctld.
> -- switch/hpe_slingshot - Fix security issue around managing VNI access.
> -- switch/nvidia_imex - Fix security issue managing IMEX channel access.
> -- switch/nvidia_imex - Allow for compatibility with job_container/tmpfs.
> * Changes in Slurm 23.11.9
> ==========================
> -- Fix many commands possibly reporting an "Unexpected Message Received" when
> in reality the connection timed out.
> -- Fix heterogeneous job components not being signaled with scancel --ctld and
> 'DELETE slurm/v0.0.40/jobs' if the job ids are not explicitly given,
> the heterogeneous job components match the given filters, and the
> heterogeneous job leader does not match the given filters.
> -- Fix regression from 23.02 impeding job licenses from being cleared.
> -- Move error to log_flag which made _get_joules_task error to be logged to the
> user when too many rpcs were queued in slurmd for gathering energy.
> -- slurmrestd - Prevent a slurmrestd segfault when modifying an association
> without specifying max TRES limits in the request if those TRES
> limits are currently defined in the association. This affects the following
> fields of endpoint 'POST /slurmdb/v0.0.38/associations/':
> 'associations/max/tres/per/job'
> 'associations/max/tres/per/node'
> 'associations/max/tres/total'
> 'associations/max/tres/minutes/per/job'
> 'associations/max/tres/minutes/total'
> -- Fix power_save operation after recovering from a failed reconfigure.
> -- scrun - Delay shutdown until after start requested. This caused scrun
> to never start or shutdown and hung forever when using --tty.
> -- Fix backup slurmctld potentially not running the agent when taking over as
> the primary controller.
> -- Fix primary controller not running the agent when a reconfigure of the
> slurmctld fails.
> -- jobcomp/{elasticsearch,kafka} - Avoid sending fields with invalid date/time.
> -- Fix energy gathering rpc counter underflow in _rpc_acct_gather_energy when
> more than 10 threads try to get energy at the same time. This prevented
> the possibility to get energy from slurmd by any step until slurmd was
> restarted, so losing energy accounting metrics in the node.
> -- slurmrestd - Fix memory leak for dbv0.0.39 jobs query which occurred if the
> query parameters specified account, association, cluster, constraints,
> format, groups, job_name, partition, qos, reason, reservation, state, users,
> or wckey. This affects the following endpoints:
> 'GET /slurmdb/v0.0.39/jobs'
> -- switch/hpe_slingshot - Fix security issue around managing VNI access.
> * Changes in Slurm 23.02.8
> ==========================
> -- Fix rare deadlock when a dynamic node registers at the same time that a
> once per minute background task occurs.
> -- Fix assertion in developer mode on a failed message unpack.
> -- switch/hpe_slingshot - Fix security issue around managing VNI access.
Slurm User Group (SLUG) 2024 is set for September 12-13 at the
University of Oslo in Oslo, Norway.
Registration information, abstracts, and travel recommendations can be
found here:https://slug24.splashthat.com/
The last day to register with standard pricing ($900) is this Friday,
August 2nd. After this, final registration will run until August 30th
at a price of $1100.
SLUG is the best way to interact with the Slurm community and to
interact with the SchedMD Support & Training staff.
Don't forget to register. We can't wait to see you in Oslo!
--
Victoria Hobson
SchedMD LLC
Vice President of Marketing
We are pleased to announce the availability of Slurm version 24.05.1.
This release addresses a number of minor-to-moderate issues since the
24.05 release was first announced a month ago.
Slurm can be downloaded from https://www.schedmd.com/downloads.php .
- Tim
> * Changes in Slurm 24.05.1
> ==========================
> -- Fix slurmctld and slurmdbd potentially stopping instead of performing a
> logrotate when recieving SIGUSR2 when using auth/slurm.
> -- switch/hpe_slingshot - Fix slurmctld crash when upgrading from 23.02.
> -- Fix "Could not find group" errors from validate_group() when using
> AllowGroups with large /etc/group files.
> -- Prevent an assertion in debugging builds when triggering log rotation
> in a backup slurmctld.
> -- Add AccountingStoreFlags=no_stdio which allows to not record the stdio
> paths of the job when set.
> -- slurmrestd - Prevent a slurmrestd segfault when parsing the crontab field,
> which was never usable. Now it explicitly ignores the value and emits a
> warning if it is used for the following endpoints:
> 'POST /slurm/v0.0.39/job/{job_id}'
> 'POST /slurm/v0.0.39/job/submit'
> 'POST /slurm/v0.0.40/job/{job_id}'
> 'POST /slurm/v0.0.40/job/submit'
> 'POST /slurm/v0.0.41/job/{job_id}'
> 'POST /slurm/v0.0.41/job/submit'
> 'POST /slurm/v0.0.41/job/allocate'
> -- mpi/pmi2 - Fix communication issue leading to task launch failure with
> "invalid kvs seq from node".
> -- Fix getting user environment when using sbatch with "--get-user-env" or
> "--export=" when there is a user profile script that reads /proc.
> -- Prevent slurmd from crashing if acct_gather_energy/gpu is configured but
> GresTypes is not configured.
> -- Do not log the following errors when AcctGatherEnergyType plugins are used
> but a node does not have or cannot find sensors:
> "error: _get_joules_task: can't get info from slurmd"
> "error: slurm_get_node_energy: Zero Bytes were transmitted or received"
> However, the following error will continue to be logged:
> "error: Can't get energy data. No power sensors are available. Try later"
> -- sbatch, srun - Set SLURM_NETWORK environment variable if --network is set.
> -- Fix cloud nodes not being able to forward to nodes that restarted with new
> IP addresses.
> -- Fix cwd not being set correctly when running a SPANK plugin with a
> spank_user_init() hook and the new "contain_spank" option set.
> -- slurmctld - Avoid deadlock during shutdown when auth/slurm is active.
> -- Fix segfault in slurmctld with topology/block.
> -- sacct - Fix printing of job group for job steps.
> -- scrun - Log when an invalid environment variable causes the job submission
> to be rejected.
> -- accounting_storage/mysql - Fix problem where listing or modifying an
> association when specifying a qos list could hang or take a very long time.
> -- gpu/nvml - Fix gpuutil/gpumem only tracking last GPU in step. Now,
> gpuutil/gpumem will record sums of all GPUS in the step.
> -- Fix error in scrontab jobs when using slurm.conf:PropagatePrioProcess=1.
> -- Fix slurmctld crash on a batch job submission with "--nodes 0,...".
> -- Fix dynamic IP address fanout forwarding when using auth/slurm.
> -- Restrict listening sockets in the mpi/pmix plugin and sattach to the
> SrunPortRange.
> -- slurmrestd - Limit mime types returned from query to 'GET /openapi/v3' to
> only return one mime type per serializer plugin to fix issues with OpenAPI
> client generators that are unable to handle multiple mime type aliases.
> -- Fix many commands possibly reporting an "Unexpected Message Received" when
> in reality the connection timed out.
> -- Prevent slurmctld from starting if there is not a json serializer present
> and the extra_constraints feature is enabled.
> -- Fix heterogeneous job components not being signaled with scancel --ctld and
> 'DELETE slurm/v0.0.40/jobs' if the job ids are not explicitly given,
> the heterogeneous job components match the given filters, and the
> heterogeneous job leader does not match the given filters.
> -- Fix regression from 23.02 impeding job licenses from being cleared.
> -- Move error to log_flag which made _get_joules_task error to be logged to the
> user when too many rpcs were queued in slurmd for gathering energy.
> -- For scancel --ctld and the associated rest api endpoints:
> 'DELETE /slurm/v0.0.40/jobs'
> 'DELETE /slurm/v0.0.41/jobs'
> Fix canceling the final array task in a job array when the task is pending
> and all array tasks have been split into separate job records. Previously
> this task was not canceled.
> -- Fix power_save operation after recovering from a failed reconfigure.
> -- slurmctld - Skip removing the pidfile when running under systemd. In that
> situation it is never created in the first place.
> -- Fix issue where altering the flags on a Slurm account (UsersAreCoords)
> several limits on the account's association would be set to 0 in
> Slurm's internal cache.
> -- Fix memory leak in the controller when relaying stepmgr step accounting to
> the dbd.
> -- Fix segfault when submitting stepmgr jobs within an existing allocation.
> -- Added "disable_slurm_hydra_bootstrap" as a possible MpiParams parameter in
> slurm.conf. Using this will disable env variable injection to allocations
> for the following variables: I_MPI_HYDRA_BOOTSTRAP,
> I_MPI_HYDRA_BOOTSTRAP_EXEC_EXTRA_ARGS, HYDRA_BOOTSTRAP,
> HYDRA_LAUNCHER_EXTRA_ARGS.
> -- scrun - Delay shutdown until after start requested. This caused scrun
> to never start or shutdown and hung forever when using --tty.
> -- Fix backup slurmctld potentially not running the agent when taking over as
> the primary controller.
> -- Fix primary controller not running the agent when a reconfigure of the
> slurmctld fails.
> -- slurmd - fix premature timeout waiting for REQUEST_LAUNCH_PROLOG with large
> array jobs causing node to drain.
> -- jobcomp/{elasticsearch,kafka} - Avoid sending fields with invalid date/time.
> -- jobcomp/elasticsearch - Fix slurmctld memory leak from curl usage
> -- acct_gather_profile/influxdb - Fix slurmstepd memory leak from curl usage
> -- Fix 24.05.0 regression not deleting job hash dirs after MinJobAge.
> -- Fix filtering arguments being ignored when using squeue --json.
> -- switch/nvidia_imex - Move setup call after spank_init() to allow namespace
> manipulation within the SPANK plugin.
> -- switch/nvidia_imex - Skip plugin operation if nvidia-caps-imex-channels
> device is not present rather than preventing slurmd from starting.
> -- switch/nvidia_imex - Skip plugin operation if job_container/tmpfs
> is configured due to incompatibility.
> -- switch/nvidia_imex - Remove any pre-existing channels when slurmd starts.
> -- rpc_queue - Add support for an optional rpc_queue.yaml configuration file.
We are pleased to announce the availability of Slurm version 23.11.8.
The 23.11.8 release fixes some potential crashes in slurmctld,
slurmrestd, and slurmd when using less common features; two issues in
auth/slurm; and a few other minor bugs.
Slurm can be downloaded from https://www.schedmd.com/downloads.php .
-Marshall
> -- Fix slurmctld crash when reconfiguring with a PrologSlurmctld is running.
> -- Fix slurmctld crash after a job has been resized.
> -- Fix slurmctld and slurmdbd potentially stopping instead of performing a
> logrotate when recieving SIGUSR2 when using auth/slurm.
> -- Fix not having a disabled value for keepalive CommunicationParameters in
> slurm.conf when these parameters are not set. This can log an error when
> setting a socket, for example during slurmdbd registration with ctld.
> -- switch/hpe_slingshot - Fix slurmctld crash when upgrading from 23.02.
> -- Fix "Could not find group" errors from validate_group() when using
> AllowGroups with large /etc/group files.
> -- slurmrestd - Prevent a slurmrestd segfault when parsing the crontab field,
> which was never usable. Now it explicitly ignores the value and emits a
> warning if it is used for the following endpoints:
> 'POST /slurm/v0.0.39/job/{job_id}'
> 'POST /slurm/v0.0.39/job/submit'
> 'POST /slurm/v0.0.40/job/{job_id}'
> 'POST /slurm/v0.0.40/job/submit'
> -- Fix getting user environment when using sbatch with "--get-user-env" or
> "--export=" when there is a user profile script that reads /proc.
> -- Prevent slurmd from crashing if acct_gather_energy/gpu is configured but
> GresTypes is not configured.
> -- Do not log the following errors when AcctGatherEnergyType plugins are used
> but a node does not have or cannot find sensors:
> "error: _get_joules_task: can't get info from slurmd"
> "error: slurm_get_node_energy: Zero Bytes were transmitted or received"
> However, the following error will continue to be logged:
> "error: Can't get energy data. No power sensors are available. Try later"
> -- Fix cloud nodes not being able to forward to nodes that restarted with new
> IP addresses.
> -- sacct - Fix printing of job group for job steps.
> -- Fix error in scrontab jobs when using slurm.conf:PropagatePrioProcess=1.
> -- Fix slurmctld crash on a batch job submission with "--nodes 0,...".
> -- Fix dynamic IP address fanout forwarding when using auth/slurm.
We are pleased to announce the availability of Slurm 24.05.0.
To highlight some new features in 24.05:
- Isolated Job Step management. Enabled on a job-by-job basis with the
--stepmgr option, or globally through SlurmctldParameters=enable_stepmgr.
- Federation - Allow for client command operation while SlurmDBD is
unavailable.
- New MaxTRESRunMinsPerAccount and MaxTRESRunMinsPerUser QOS limits.
- New USER_DELETE reservation flag.
- New Flags=rebootless option on Features for node_features/helpers
which indicates the given feature can be enabled without rebooting the node.
- Cloud power management options: New "max_powered_nodes=<limit>" option
in SlurmctldParamters, and new SuspendExcNodes=<nodes>:<count> syntax
allowing for <count> nodes out of a given node list to be excluded.
- StdIn/StdOut/StdErr now stored in SlurmDBD accounting records for
batch jobs.
- New switch/nvidia_imex plugin for IMEX channel management on NVIDIA
systems.
- New RestrictedCoresPerGPU option at the Node level, designed to ensure
GPU workloads always have access to a certain number of CPUs even when
nodes are running non-GPU workloads concurrently.
The Slurm documentation has also been updated to the 24.05 release.
(Older versions can be found in the archive, linked from the main
documentation page.)
Slurm can be downloaded from https://www.schedmd.com/downloads.php .
--
Marshall Garey
Release Management, Support, and Development
SchedMD LLC - Commercial Slurm Development and Support
Slurm User Group (SLUG) 2024 is set for September 12-13 at the
University of Oslo in Oslo, Norway.
Registration information and a high-level schedule can be found
here:https://slug24.splashthat.com/ The last day to register at the
early bird pricing is this Friday, May 31st.
Friday is also the deadline to submit a presentation abstract. We do
not intend to extend this deadline.
If you are interested in presenting your own usage, developments, site
report, tutorial, etc about Slurm, please fill out the following
form:https://forms.gle/N7bFo5EzwuTuKkBN7
Notifications of final presentations accepted will go out by Friday, June 14th.
--
Victoria Hobson
SchedMD LLC
Vice President of Marketing
We are pleased to announce the availability of Slurm version 23.11.7.
The 23.11.7 release fixes a few potential crashes in slurmctld when
using less common options on job submission, slurmrestd compatibility
with auth/slurm, and some additional minor and moderate severity bugs.
Slurm can be downloaded from https://www.schedmd.com/downloads.php .
-Marshall
> -- slurmrestd - Correct OpenAPI specification for
> 'GET /slurm/v0.0.40/jobs/state' having response as null.
> -- Allow running jobs on overlapping partitions if jobs don't specify -s.
> -- Fix segfault when requesting a shared gres along with an exclusive
> allocation.
> -- Fix regression in 23.02 where afternotok and afterok dependencies were
> rejected for federated jobs not running on the origin cluster of the
> submitting job.
> -- slurmctld - Disable job table locking while job state cache is active when
> replying to `squeue --only-job-state` or `GET /slurm/v0.0.40/jobs/state`.
> -- Fix sanity check when setting tres-per-task on the job allocation as well as
> the step.
> -- slurmrestd - Fix compatiblity with auth/slurm.
> -- Fix issue where TRESRunMins gets off correct value if using
> QOS UsageFactor != 1.
> -- slurmrestd - Require `user` and `association_condition` fields to be
> populated for requests to 'POST /slurmdb/v0.0.40/users_association'.
> -- Avoid a slurmctld crash with extra_constraints enabled when a job requests
> certain invalid --extra values.
> -- `scancel --ctld` and `DELETE /slurm/v0.0/40/jobs` - Fix support for job
> array expressions (e.g. 1_[3-5]). Also fix signaling a single pending array
> task (e.g. 1_10), which previously signaled the whole array job instead.
> -- Fix a possible slurmctld segfault when at some point we failed to create an
> external launcher step.
> -- Allow the slurmctld to open a connection to the slurmdbd if the first
> attempt fails due to a protocol error.
> -- mpi/cray_shasta - Fix launch for non-het-steps within a hetjob.
> -- sacct - Fix "gpuutil" TRES usage output being incorrect when using --units.
> -- Fix a rare deadlock on slurmctld shutdown or reconfigure.
> -- Fix issue that only left one thread on each core available when "CPUs=" is
> configured to total thread count on multi-threaded hardware and no other
> topology info ("Sockets=", "CoresPerSocket", etc.) is configured.
> -- Fix the external launcher step not being allocated a VNI when requested.
> -- jobcomp/kafka - Fix payload length when producing and sending a message.
> -- scrun - Avoid a crash if RunTimeDelete is called before the container
> finishes.
> -- Save the slurmd's cred_state while reconfiguring to prevent the loss job
> credentials.
Slurm User Group (SLUG) 2024 is set for September 12-13 at the
University of Oslo in Oslo, Norway.
Registration information and a high-level schedule can be found
here:https://slug24.splashthat.com/
The deadline to submit a presentation abstract is Friday, May 31st. We
do not intend to extend this deadline.
If you are interested in presenting your own usage, developments, site
report, tutorial, etc about Slurm, please fill out the following
form:https://forms.gle/N7bFo5EzwuTuKkBN7
Notifications of final presentations accepted will go out by Friday, June 14th.
--
Victoria Hobson
SchedMD LLC
Vice President of Marketing
We are pleased to announce the availability of Slurm release candidate
24.05.0rc1.
To highlight some new features coming in 24.05:
- (Optional) isolated Job Step management. Enabled on a job-by-job basis
with the --stepmgr option, or globally through
SlurmctldParameters=enable_stepmgr.
- Federation - Allow for client command operation while SlurmDBD is
unavailable.
- New MaxTRESRunMinsPerAccount and MaxTRESRunMinsPerUser QOS limits.
- New USER_DELETE reservation flag.
- New Flags=rebootless option on Features for node_features/helpers
which indicates the given feature can be enabled without rebooting the node.
- Cloud power management options: New "max_powered_nodes=<limit>" option
in SlurmctldParamters, and new SuspendExcNodes=<nodes>:<count> syntax
allowing for <count> nodes out of a given node list to be excluded.
- StdIn/StdOut/StdErr now stored in SlurmDBD accounting records for
batch jobs.
- New switch/nvidia_imex plugin for IMEX channel management on NVIDIA
systems.
- New RestrictedCoresPerGPU option at the Node level, designed to ensure
GPU workloads always have access to a certain number of CPUs even when
nodes are running non-GPU workloads concurrently.
This is the first release candidate of the upcoming 24.05 release
series, and represents the end of development for this release, and a
finalization of the RPC and state file formats.
If any issues are identified with this release candidate, please report
them through https://bugs.schedmd.com against the 24.05.x version and we
will address them before the first production 24.05.0 release is made.
Please note that the release candidates are not intended for production use.
A preview of the updated documentation can be found at
https://slurm.schedmd.com/archive/slurm-master/ .
Slurm can be downloaded from https://www.schedmd.com/downloads.php .
--
Marshall Garey
Release Management, Support, and Development
SchedMD LLC - Commercial Slurm Development and Support
We are pleased to announce the availability of Slurm version 23.11.6.
The 23.11.6 release includes two different problems with the
priority/multifactor plugin: a crash and a miscalculation of
AssocGrpCPURunMinutes after a slurmctld reconfiguration/restart.
The wsrep_on errors that sites running MySQL or older MariaDB should
happen much less frequently and has a clarifying statement when it
is an innocuous error.
Slurm can be downloaded from https://www.schedmd.com/downloads.php .
-Marshall
> * Changes in Slurm 23.11.6
> ==========================
> -- Avoid limiting sockets per node to one when using gres enforce-binding.
> -- slurmrestd - Avoid permission denied errors when attempting to listen on
> the same port multiple times.
> -- Fix GRES reservations where the GRES has no topology
> (no cores= in gres.conf).
> -- Ensure that thread_id_rpc is gone before priority_g_fini().
> -- Fix scontrol reboot timeout removing drain state from nodes.
> -- squeue - Print header on empty reponse to `--only-job-state`.
> -- Fix slurmrestd not ending job properly when xauth is not present and a x11
> job is sent.
> -- Add experimental job state caching with
> SchedulerParameters=enable_job_state_cache to speed up querying job states
> with squeue --only-job-state.
> -- slurmrestd - Correct dumping of invalid ArrayJobIds returned from
> 'GET /slurm/v0.0.40/jobs/state'.
> -- squeue - Correct dumping of invalid ArrayJobIds returned from
> `squeue --only-job-state --{json|yaml}`.
> -- If scancel --ctld is not used with --interactive, --sibling, or specific
> step ids, then this option issues a single request to the slurmctld to
> signal all jobs matching the specified filters. This greatly improves
> the performance of slurmctld and scancel. The updated --ctld option also
> fixes issues with the --partition or --reservation scancel options for jobs
> that requested multiple partitions or reservations.
> -- slurmrestd - Give EINVAL error when failing to parse signal name to numeric
> signal.
> -- slurmrestd - Allow ContentBody for all methods per RFC7230 even if ignored.
> -- slurmrestd - Add 'DELETE /slurm/v0.0.40/jobs' endpoint to allow bulk job
> signaling via slurmctld.
> -- Fix combination of --nodelist and --exclude not always respecting the
> excluded node list.
> -- Fix jobs incorrectly allocating nodes exclusively when started on a
> partition that doesn't enforce it. This could happen if a multi-partition
> job doesn't specify --exclusive and is evaluated first on a partition
> configured with OverSubscribe=EXCLUSIVE but ends up starting in a partition
> configured with OverSubscribe!=EXCLUSIVE evaluated afterwards.
> -- Setting GLOB_SILENCE flag no longer exposes old bugged behavior.
> -- Fix associations AssocGrpCPURunMinutes being incorrectly computed for
> running jobs after a controller reconfiguration/restart.
> -- Fix scheduling jobs that request --gpus and nodes have different node
> weights and different numbers of gpus.
> -- slurmrestd - Add "NO_CRON_JOBS" as possible flag value to the following:
> 'DELETE /slurm/v0.0.40/jobs' flags field.
> 'DELETE /slurm/v0.0.40/job/{job_id}?flags=' flags query parameter.
> -- Fix scontrol segfault/assert failure if the TRESPerNode parameter is used
> when creating reservations.
> -- Avoid checking for wsrep_on when restoring streaming replication settings.
> -- Clarify in the logs that error "1193 Unknown system variable 'wsrep_on'" is
> innocuous.
> -- accounting_storage/mysql - Fix problem when loading reservations from an
> archive dump.
> -- slurmdbd - Fix minor race condition when sending updates to a shutdown
> slurmctld.
> -- slurmctld - Fix invalid refusal of a reservation update.
> -- openapi - Fix memory leak of /meta/slurm/cluster response field.
> -- Fix memory leak when using auth/slurm and AuthInfo=use_client_ids.
--
Marshall Garey
Release Management, Support, and Development
SchedMD LLC - Commercial Slurm Development and Support