Ticket 517 - SLURM_* variables differ in prolog, task-prolog, task-epilog, epilog
Summary: SLURM_* variables differ in prolog, task-prolog, task-epilog, epilog
Status: RESOLVED DUPLICATE of ticket 515
Alias: None
Product: Slurm
Classification: Unclassified
Component: Scheduling (show other tickets)
Version: 2.6.x
Hardware: Linux Linux
: 5 - Enhancement
Assignee: Moe Jette
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2013-11-15 05:41 MST by David Kemeza
Modified: 2013-11-15 05:51 MST (History)
2 users (show)

See Also:
Site: NASA - NCCS
Slinky Site: ---
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
Google sites: ---
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 David Kemeza 2013-11-15 05:41:11 MST 
There are some SLURM_* variables that are set in the prolog's environment that are not carried through to the task-prolog, the job's, task-epilog, and epilog environments.  
These would be nice to have to be able to trigger of these variables at every level of the job setup and teardown.

I'd like to see the following variables carried through the environment as it passes through the various phases.

SLURM_CLUSTER or SLURM_CLUSTERNAME (I think would need to be added)

SLURM_PARTITION This appears in the prolog and epilog environment but not in the task-prolog's or task-epilog's environment

SLURM_JOB_USER only appears in prolog, task-epilog, and epilog
Comment 1 David Bigagli 2013-11-15 05:51:53 MST 
Duplicate 515

*** This ticket has been marked as a duplicate of ticket 515 ***