Bug 845567

Summary: new PRE_SKIP key word in DAGMan
Product: Red Hat Enterprise MRG Reporter: Martin Kudlej <mkudlej>
Component: condorAssignee: Timothy St. Clair <tstclair>
Status: CLOSED ERRATA QA Contact: Luigi Toscano <ltoscano>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.2CC: ltoscano, matt, pmackinn, rrati, tstclair
Target Milestone: 2.3Keywords: FutureFeature, Rebase, TestOnly
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: condor-7.8.2-0.2 Doc Type: Rebase: Enhancements Only
Doc Text:
Important: if this rebase also contains *bug fixes* (or contains only bug fixes), select the correct option from the Doc Type drop-down list. Rebase package(s) to version: condor-7.8 series Highlights and notable enhancements: In a DAGMan job, if a PRE script exits with the PRE_SKIP value, then the node succeeds and the job and the POST script are both skipped.
Story Points: ---
Clone Of:
: 876617 (view as bug list) Environment:
Last Closed: 2013-03-06 13:44:50 EST Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 845292, 876617    

Description Martin Kudlej 2012-08-03 09:08:09 EDT
Description of problem:
We have discovered the following undocumented fix in the 2.2 builds and t needs to be explicitly tested:

The  new PRE_SKIP key word in DAGMan changes the behavior of DAG node  execution such that the node's job and POST script may be skipped based  on the exit value of the PRE script. See section 2.10.2 for details.  (Ticket #2122).
Comment 3 Timothy St. Clair 2012-08-07 15:20:42 EDT
ref for testing http://research.cs.wisc.edu/condor/manual/v7.8/2_10DAGMan_Applications.html#4576
Comment 6 Luigi Toscano 2013-01-28 13:32:50 EST
The PRE_SKIP value is correctly taken into account, if specified. It affects the termination of the associated job according the documentation.

Verified on RHEL5.9/6.4 beta, i386/x86_64.
Comment 8 errata-xmlrpc 2013-03-06 13:44:50 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.