Bug 4391 - Continuation of job_submit/lua slurm.log_user() for job updates
Summary: Continuation of job_submit/lua slurm.log_user() for job updates
Status: RESOLVED DUPLICATE of bug 14539
Alias: None
Product: Slurm
Classification: Unclassified
Component: slurmctld (show other bugs)
Version: 18.08.x
Hardware: Linux Linux
: --- 5 - Enhancement
Assignee: Alejandro Sanchez
QA Contact:
: 5149 (view as bug list)
Depends on:
Reported: 2017-11-16 03:48 MST by Alejandro Sanchez
Modified: 2023-01-04 07:19 MST (History)
2 users (show)

See Also:
Site: SchedMD
Alineos Sites: ---
Bull/Atos Sites: ---
Confidential Site: ---
Cray Sites: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ---
OCF Sites: ---
SFW Sites: ---
SNIC sites: ---
Linux Distro: ---
Machine Name:
CLE Version:
Version Fixed:
Target Release: ---
DevPrio: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Alejandro Sanchez 2017-11-16 03:48:38 MST
Coming from bug 4038, we made the output of slurm.log_user() available for the user clients even on "return slurm.SUCCESS". This bug should track the continuation work to make the output also available when the function is called from within the lua function slurm_job_modify (triggered on scontrol update job).
Comment 1 Alejandro Sanchez 2018-01-03 07:37:27 MST
Also we've noticed that if you have for instance 'defer' in SchedulerParameters, and/or if the nodes are set to DRAIN when you submit the job, then eventually you resume the nodes, the job submit user_msg isn't sent back to the user. If we look for instance at the _slurm_rpc_allocate_resources func, at the end of it there's the send_msg: goto tag. If the job is waiting for resources, the execution goes through the reject_job=true path, and no RESPONSE_RESOURCE_ALLOCATION is sent back (or the pack or will run analogous response), instead just the slurm_send_rc_[err]_msg, thus not including the new job_submit_user_msg member.
Comment 2 Alejandro Sanchez 2018-05-09 01:20:15 MDT
*** Bug 5149 has been marked as a duplicate of this bug. ***
Comment 3 Alejandro Sanchez 2018-05-09 01:20:47 MDT
Take into account the changes made in 3f4cde9c from bug 5106.
Comment 4 Alejandro Sanchez 2023-01-04 07:19:34 MST
Marking as duplicate.

*** This bug has been marked as a duplicate of bug 14539 ***