Fix jobcompletion logfile existance #103
Merged
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.
Setting
openhpc_slurm_job_comp_type(slurm.conf parameterJobCompType) tojobcomp/filetxtenables job completion records, which can be viewed usingsacct -c. This is much more limited than full accounting info, but could be useful now Slurm 20.11 doesn't support filetxt accounting storage and enabling accounting requires deploying/configuring mysql + slurmdbd (hence b3b4f44 disabling accounting by default).This PR fixes the runtime play so that the job completion logfile (role var
openhpc_slurm_job_comp_loc, slurm.conf parameterJobCompLoc) is writable by userslurm. Without it slurmctld fails on startup with a message like:It also adds
molecule/test12for this usingopenhpc_slurm_job_comp_type: jobcomp/filetxtand role defaultopenhpc_slurm_job_comp_loc, and updates the README to clarify why you might want to use this.Closes #102 which contains lots of info re. slurm behavior, probably mostly not relevant here.