Bug 700837

Summary:	New job fails if Release Action == Power Off
Product:	[Retired] Beaker	Reporter:	Alexander Todorov <atodorov>
Component:	lab controller	Assignee:	Bill Peck <bpeck>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.6	CC:	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-09-28 15:20:42 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 Alexander Todorov 2011-04-29 14:54:15 UTC

Description of problem:

In beaker webUI go to the system power settings and select
type = virsh
release action = power off

After I provision the system for the first time and cancel the job it shuts down. Then I schedule new job (provision again) and it fails. 

On the lab controller (/var/log/cobbler/tasks/) I see that initial poweroff failed. Cobbler tries to execute:

# /usr/bin/virsh --connect qemu+ssh://root.com/system destroy tester1

And gets the error:

error: Failed to destroy domain tester1
error: Requested operation is not valid: domain is not running


Version-Release number of selected component (if applicable):
cobbler-2.0.10-1.el5
beaker-server-0.6.8-5.el5

How reproducible:
always

Steps to Reproduce:
1. add to the lab a virtual system and configure remote power using virsh
2. configure release action = power off
3. Perform 1 test job and cancel it (or wait until it completes)
4. Start new job
  
Actual results:
New job fails

Expected results:
New job starts.

Additional info:

Comment 1 Bill Peck 2011-09-28 15:20:42 UTC

I pushed an update to the power_virsh template last week and mgregg confirmed it fixes this problem.