Bug 726761 - Exit Hook message not sent by carod when file_no_perms.py runs
Summary: Exit Hook message not sent by carod when file_no_perms.py runs
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: condor-low-latency
Version: Development
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: 2.1
: ---
Assignee: Robert Rati
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-29 18:11 UTC by Robert Rati
Modified: 2011-09-30 19:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-30 19:26:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Robert Rati 2011-07-29 18:11:47 UTC 
Description of problem:
The file_no_perms.py test expects 2 messages, 1 from the reply fetch and 1 from the exit hook upon failure.  The starterlog shows an invocation of the Exit Hook:

 07/29/11 18:13:26 HOOK_JOB_EXIT (/usr/libexec/condor/hooks/hook_job_exit.py) invoked with reason: "evict"

However, carod's log does not show invocation of handle_job_exit.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Robert Rati 2011-09-08 14:16:12 UTC 
This is actually a mistake in the test.  The code in condor is unchanged from 7.4.5.  The starter is excepting because it is unable to execute the job, and part of the cleanup process ends up invoking the exit hook.  However, the starter finishes cleaning up and exits before the exit hook completes.  I verified that the same error case occurs in 7.4.5.
Comment 2 Robert Rati 2011-09-08 19:04:24 UTC 
Test is fixed on branch:
BZ726761-noperms-test-fix
Note You need to log in before you can comment on or make changes to this bug.