Bug 726761

Summary:	Exit Hook message not sent by carod when file_no_perms.py runs
Product:	Red Hat Enterprise MRG	Reporter:	Robert Rati <rrati>
Component:	condor-low-latency	Assignee:	Robert Rati <rrati>
Status:	CLOSED UPSTREAM	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	Development	CC:	ltrilety, matt, mkudlej
Target Milestone:	2.1
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-09-30 19:26:47 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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