Bug 822887 - Beaker job should change status to completed when all recipes are in status completed (or aborted)
Summary: Beaker job should change status to completed when all recipes are in status c...
Keywords:
Status: CLOSED DUPLICATE of bug 807237
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: 0.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Raymond Mancy
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-18 12:18 UTC by Jiří Mikulka
Modified: 2014-12-08 01:12 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-25 05:19:49 UTC
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.