Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 459615

Summary: Job Hooks do not provide correct JobStatus in ClassAds
Product: Red Hat Enterprise MRG Reporter: Robert Rati <rrati>
Component: gridAssignee: Robert Rati <rrati>
Status: CLOSED ERRATA QA Contact: Martin Kudlej <mkudlej>
Severity: medium Docs Contact:
Priority: low    
Version: 1.0CC: lbrindle, matt, mkudlej
Target Milestone: 1.2   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Grid bug fix C: The classad information in the job exit hook and status hook do not correctly reflect the state of the job. C: Status is always returned as 1, regardless of the actual status F: Responses sent to the reply-to queue now have the JobStatus set R: The status is now accurate The ClassAd information in the job exit hook and status hook do not correctly reflect the state of the job, always returning 1, regardless of the actual status. The responses sent to the reply-to queue now have the JobStatus set and the reported status is now accurate.
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-12-03 09:19:43 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:
Bug Depends On:    
Bug Blocks: 489006, 527551    

Description Robert Rati 2008-08-20 15:36:35 UTC
Description of problem:
The classad information the job exit hook and status hook provide do not correctly reflect the state of the job.  In the provided job classad, the JobStatus is always 1, even if the job is running or has completed.

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 2009-02-27 16:04:14 UTC
Responses sent to the reply-to queue now have the JobStatus set.

Fixed in:
condor-low-latency-1.0-10

Comment 3 Irina Boverman 2009-10-29 14:29:31 UTC
Release note added. If any revisions are required, please set the 
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

New Contents:
please see bug summary.

Comment 4 Lana Brindley 2009-11-04 02:35:47 UTC
Release note updated. If any revisions are required, please set the 
"requires_release_notes"  flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

Diffed Contents:
@@ -1 +1,3 @@
+Grid bug fix
+
 please see bug summary.

Comment 5 Lana Brindley 2009-11-04 03:21:35 UTC
Release note updated. If any revisions are required, please set the 
"requires_release_notes"  flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

Diffed Contents:
@@ -1,3 +1,8 @@
 Grid bug fix
 
-please see bug summary.+C: The classad information in the job exit hook and status hook do not correctly reflect the state of the job.
+C: Status is always returned as 1, regardless of the actual status
+F: Responses sent to the reply-to queue now have the JobStatus set
+R: The status is now accurate
+
+The ClassAd information in the job exit hook and status hook do not correctly reflect the state of the job, always returning 1, regardless of the actual status. The responses sent to the reply-to queue now have the JobStatus set and the reported status is now accurate.

Comment 6 Martin Kudlej 2009-11-06 13:21:15 UTC
Tested on RHEL 5.4 x86_64 with condor-low-latency-1.0-9.el5 and condor-job-hooks-common-1.0-5.el5 and it doesn't work.
Tested on RHEL 5.4/4.8 x i386/x86_64 with condor-low-latency-1.0-21 and condor-job-hooks-1.0-13 and JobState, JobStatus and "Exit" job classadds were there.
-->VERIFIED

Comment 8 errata-xmlrpc 2009-12-03 09:19:43 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2009-1633.html