Bug 1047944

Summary: Can't poweroff or destroy virtual machine via vdsClient after sysprep attached
Product: Red Hat Enterprise Virtualization Manager Reporter: Artyom <alukiano>
Component: vdsmAssignee: Nobody <nobody>
Status: CLOSED DUPLICATE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: abaron, bazulay, hateya, iheim, istein, lpeer, ofrenkel, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-05 08:30:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
vdsm.log
none
host_1 logs none

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.