Bug 822887

Summary:	Beaker job should change status to completed when all recipes are in status completed (or aborted)
Product:	[Retired] Beaker	Reporter:	Jiří Mikulka <jmikulka>
Component:	web UI	Assignee:	Raymond Mancy <rmancy>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.8	CC:	bpeck, dcallagh, ebaak, mishin, mminar, rmancy, stl
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-10-25 05:19:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jiří Mikulka 2012-05-18 12:18:25 UTC

Description of problem:
A job with 4 recipes (https://beaker.engineering.redhat.com/jobs/233355) was scheduled in Beaker and after all recipes finished and were in status Completed (or Aborted), Beaker should change the status of the Job to Completed too, but it's still is Running state.

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

How reproducible:


Steps to Reproduce:
1. provision job with more recipes
2. wait until all recipes finish
3. check status of the job
  
Actual results:
recipes are in Completed/Aboreted status, but job is in Running status

Expected results:
both recipes and job should be in Completed status

Additional info:

Comment 1 Dan Callaghan 2012-10-25 05:19:49 UTC


*** This bug has been marked as a duplicate of bug 807237 ***