Open jedel1043 opened 3 months ago
Can reproduce. I consider this a bug since after some period of time a site may choose to directly use the file rather than use the config server.
Setting config-server
should unstage any set slurm.conf file that may have been pre-configured. For example, this could be a simple file rename like $SNAP_COMMON/etc/slurm/slurm.conf
-> $SNAP_COMMON/etc/slurm/slurm.conf.bak
. This way the slurm.conf configuration file in conf-cache/
will supersede the original configuration, but will preserve the original configuration should the administrator decide to unset config-server
.
A warning message can be emitted if trying to set slurm.conf configurations when configless mode is enabled on slurmd that states that options will not be applied. Then, if config-server
is unset, the configure hook could restore slurm.conf.bak
As for the .env file itself, the config-server option should be unset to indicate to slurmd wrapper that we're no longer running in configless mode and instead are running in traditional (or potentially dynamic) mode.
To reproduce