Ticket 8172 - Recording submission host in job record
Summary: Recording submission host in job record
Status: OPEN
Alias: None
Product: Slurm
Classification: Unclassified
Component: Accounting (show other tickets)
Version: 18.08.8
Hardware: Linux Linux
: 5 - Enhancement
Assignee: Unassigned Developer
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2019-12-02 09:59 MST by Stuart Rankin
Modified: 2025-02-27 10:11 MST (History)
2 users (show)

See Also:
Site: Cambridge
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ---
NoveTech Sites: ---
Nvidia HWinf-CS Sites: ---
OCF Sites: ---
Recursion Pharma Sites: ---
SFW Sites: ---
SNIC sites: ---
Tzag Elita Sites: ---
Linux Distro: ---
Machine Name:
CLE Version:
Version Fixed:
Target Release: ---
DevPrio: ---
Emory-Cloud Sites: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this ticket.
Description Stuart Rankin 2019-12-02 09:59:24 MST 
Hi,

As far as I can see, the slurm DB doesn't currently record the submission host in the record for each batch job. This would have been useful information recently when we were trying to understand the origin of a set of root-owned jobs that we noticed in our own database. More generally, it would be potentially useful information when debugging user job issues (in our case we have 20+ login nodes).

I would like to request that this information be added in a future release of SLURM.

Secondly, in the potentially worrying case where root has executed as an ordinary user via --uid, it would be useful if this was made clear in the job entry, e.g. by adding either a "submituser" field or an "effectiveuser" field so that both the relevant userids are recorded.

Many thanks for your attention -

Best regards

Stuart