Bug 1047944 - Can't poweroff or destroy virtual machine via vdsClient after sysprep attached
Summary: Can't poweroff or destroy virtual machine via vdsClient after sysprep attached
Keywords:
Status: CLOSED DUPLICATE of bug 1047356
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-02 16:37 UTC by Artyom
Modified: 2014-01-06 13:28 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-05 08:30:00 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
vdsm.log (63.51 KB, text/x-log)
2014-01-02 16:37 UTC, Artyom 		no flags Details
host_1 logs (2.88 MB, application/zip)
2014-01-06 13:28 UTC, Ilanit Stein 		no flags Details
View All

Description Artyom 2014-01-02 16:37:03 UTC 
Created attachment 844617 [details]
vdsm.log

Description of problem:
Can't poweroff or destroy virtual machine via vdsClient after sysprep attached.

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

How reproducible:
Always

Steps to Reproduce:
1. Create new vm and choose as OS Windows 7 x64
2. Run once vm with floppy enabled and attach [sysprep]
3. Try to poweroff virtual machine

Actual results:
Error: "Failed to power off VM windows_vm" and vm still up. 

Expected results:
Vm must poweroff correctly


Additional info:
Trying to destroy vm via vdsClient also failed, and the only one possible way to poweroff vm, it to restart host with it and "Confirm reboot"
If you will migrate this vm, you will have two vms on source and destination hosts that you can't poweroff.
Comment 1 Omer Frenkel 2014-01-05 08:30:00 UTC 

*** This bug has been marked as a duplicate of bug 1047356 ***
Comment 2 Ilanit Stein 2014-01-06 13:28:04 UTC 
Created attachment 846083 [details]
host_1 logs

host time 2 hours behind rhevm time.
Note You need to log in before you can comment on or make changes to this bug.