Bug 718313

Summary:	harness can run next recipe on the previous install
Product:	[Retired] Beaker	Reporter:	Bill Peck <bpeck>
Component:	scheduler	Assignee:	Bill Peck <bpeck>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	high
Version:	0.6	CC:	atodorov, bpeck, dcallagh, mcsontos, 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:	2011-07-14 02:07:18 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 Bill Peck 2011-07-01 19:04:08 UTC

Description of problem:
If the system is left running and beah is running there is a short window where the system can start running a recipe before the power command can cause the system to reboot to install.

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

How reproducible:
sometimes

Steps to Reproduce:
1. set a system to leave power on
2. depending on how long before power command executes
3. system will start running new recipe before provisioning
  

Suggestion is to update harness and scheduler to use recipeid instead of hostname.  Should still support running via hostname so we can support non-install test runs.

Comment 1 Bill Peck 2011-07-01 20:44:15 UTC

Pushed the server side chnages to gerrit.

Comment 2 Marian Csontos 2011-07-07 17:01:45 UTC

Pushed client side changes to gerrit.
After tweaking LC a bit verified to work.