Ticket 451 - Provide both the '-r' and '-a' options on each call to xtcleanup_after
Summary: Provide both the '-r' and '-a' options on each call to xtcleanup_after
Status: RESOLVED FIXED
Alias: None
Product: Slurm
Classification: Unclassified
Component: Cray ALPS (show other tickets)
Version: 14.03.x
Hardware: Linux Linux
: 5 - Enhancement
Assignee: Danny Auble
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2013-10-09 09:23 MDT by Jason Sollom
Modified: 2013-10-10 05:02 MDT (History)
1 user (show)

See Also:
Site: CRAY
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

Note You need to log in before you can comment on or make changes to this ticket.
Description Jason Sollom 2013-10-09 09:23:16 MDT
The Node Health developers would like the select_cray plugin to use both the -r and -a options when invoking xtcleanup_after.

The -r option provides the reservation information also known as the Job ID.
The -a option provides the application information also known as the APID, which is the combination of Job ID and Step ID.

The -r and -a options do not control which mode xtcleanup_after runs in.  The -m option controls whether xtcleanup_after is in 'end of step' mode or 'end of job' mode.

The developers would like both pieces of information present for every invocation of xtcleanup_after.
Comment 1 Danny Auble 2013-10-09 09:29:15 MDT
If there is no stepid (meaning end of job) what is the APID?
Comment 2 Jason Sollom 2013-10-10 04:27:59 MDT
(In reply to Danny Auble from comment #1)
> If there is no stepid (meaning end of job) what is the APID?

An APID equal to zero is appropriate in this case.
Comment 3 Danny Auble 2013-10-10 05:02:38 MDT
Excellent, that was my assumption as well.

This is completely fixed along with the xfree mess-up in bug 450 after commit cccd7163296c8fd618c6f590609e60d3b8cce382 on the master.

Let me know if this isn't done like the NHC developers expect.