Bug 700837 - New job fails if Release Action == Power Off
Summary: New job fails if Release Action == Power Off
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: lab controller
Version: 0.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: Bill Peck
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-29 14:54 UTC by Alexander Todorov
Modified: 2019-05-22 13:40 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-28 15:20:42 UTC


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.