Bug 758593

Summary:	Wrong report email send from beaker
Product:	[Retired] Beaker	Reporter:	Qian Hong <qhong>
Component:	reports	Assignee:	Dan Callaghan <dcallagh>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.7	CC:	bpeck, dcallagh, kzhang, mcsontos, rmancy, stl
Target Milestone:	future_maint
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-05 10:33:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Qian Hong 2011-11-30 07:18:56 UTC

Description of problem:
1. 2011-11-29 10:26 pm
test-auto sent an email to me and told me Job 163873's Status is "Completed/Pass" 
2. by manually check on Web UI, I found that the real status of Job 163873[1] is "Running/Pass" (server is running, client is complete)
3. After manually cancel the job on Web UI, test-auto sent me another emails, told me the Status is "Completed/Warn"

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


How reproducible:
1/1, not sure if it is always reproducible

Steps to Reproduce:
Submit Job 163873 from beaker command line tool.
  
Actual results:
Sent the result email to me before the job is complete

Expected results:
Sent the result email to me after the job is complete

Additional info:
In this special case, the job may fail (timeout) if I didn't cancel it manually. 


[1] https://beaker.engineering.redhat.com/jobs/163873

Comment 1 Bill Peck 2011-12-01 18:46:03 UTC

I think this is the same issue where we saw jobs left in a running state.  It must be that we are hitting some error which causes the db to roll the transaction back.  Thats why the email was sent but the job was still "running".

Comment 3 Dan Callaghan 2012-06-05 10:33:06 UTC

Closing this as it seems to have been a one-off. If anyone has more information about this same issue, please re-open.