Ticket 1036

Summary:	--export=NONE fixed in slurm-14., not in slurm-2.6.
Product:	Slurm	Reporter:	Thomas Cadeau <thomas.cadeau>
Component:	Other	Assignee:	Moe Jette <jette>
Status:	RESOLVED INFOGIVEN	QA Contact:
Severity:	3 - Medium Impact
Priority:	---	CC:	da, yiannis.georgiou
Version:	2.6.6
Hardware:	Linux
OS:	Linux
Site:	Atos/Eviden Sites	Alineos Sites:	---
Atos/Eviden Sites:	---	Confidential Site:	---
Coreweave sites:	---	Cray Sites:	---
DS9 clusters:	---	HPCnow Sites:	---
HPE Sites:	---	IBM Sites:	---
NOAA SIte:	---	OCF Sites:	---
Recursion Pharma Sites:	---	SFW Sites:	---
SNIC sites:	---	Linux Distro:	---
Machine Name:		CLE Version:
Version Fixed:		Target Release:	---
DevPrio:	---	Emory-Cloud Sites:	---
Attachments:	backport of sbatch --export=NONE fix for Slurm v2.6

Description Thomas Cadeau 2014-08-11 20:02:59 MDT

Hi,
I found the commit:

commit 9b4f363456fe99629603386f57331f1a5011d6f3
Author: Morris Jette <jette@schedmd.com>
Date:   Sun Mar 16 15:55:44 2014 -0700

    Export "SLURM*" env vars if --export=NONE
    
    Previously if the sbatch --export=NONE option was used then several
    Slurm environment variables were not propagated from the sbatch
    command (SLURM_SUBMIT_DIR, SLURM_SUBMIT_HOST, SLURM_JOB_NAME, etc.)

Can you add this correction to slurm-2.6.**?

Thomas

Comment 1 Moe Jette 2014-08-12 03:52:44 MDT

Created attachment 1132 [details]
backport of sbatch --export=NONE fix for Slurm v2.6

Comment 2 Moe Jette 2014-08-12 04:00:28 MDT

The last release of version 2.6 was five months ago and we have no expectation of making any more releases. I have attached a patch of this applied to version 2.6, which can be used as a site-local patch if desired.

I also committed this patch to the slurm-2.6 branch in github if someone wants to work from that instead.