SCHED-1522 Rename slurm.config->autogen_slurm.conf + add warning comment#2573
Open
ChessProfessor wants to merge 3 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Customers can edit Slurm config files directly inside jail/login environments, but those files are generated and later overwritten by Soperator controllers. This makes local changes non-persistent and easy to lose without an obvious warning.
Solution
Added clear managed-file warnings to generated Slurm configs. Kept /etc/slurm/slurm.conf as the default entrypoint, but made it a warning-only stub that includes generated autogen_slurm.conf. Renamed custom_slurm.conf to override_slurm.conf to make customer override intent clearer. Updated related Terraform
wording.
Testing
Added new test + e2e run https://github.com/nebius/soperator/actions/runs/27006234596
Release Notes