Ticket 856

Summary: add new job state for dependency never satisfied
Product: Slurm Reporter: Moe Jette <jette>
Component: SchedulingAssignee: David Bigagli <david>
Status: RESOLVED FIXED QA Contact:
Severity: 4 - Minor Issue    
Priority: --- CC: da
Version: 14.11.x   
Hardware: Linux   
OS: Linux   
Site: SchedMD 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: 14.11.0pre2
Target Release: --- DevPrio: ---
Emory-Cloud Sites: ---

Description Moe Jette 2014-06-04 06:00:37 MDT 
If a job can never run due to dependencies not being satisfied (e.g. "afterok:123" and job 123 fails), then do not abort the job. Instead put the job into some new state (job state flag, something like "DependencyNotSatisfied"). This will permit someone to clear the dependency later and let the job run.

This could be related to bug 855.
While this is an enhancement, I make making this severity 4.
Comment 1 David Bigagli 2014-06-16 10:42:01 MDT 
Fixed in commit:8e00783b50

David