Bug 1155705

Summary: Failed to power off VM VM1-strass
Product: Red Hat Enterprise Virtualization Manager Reporter: Nikolai Sednev <nsednev>
Component: ovirt-engineAssignee: Nobody <nobody>
Status: CLOSED DUPLICATE QA Contact:
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: ecohen, gklein, iheim, lpeer, lsurette, ofrenkel, rbalakri, Rhev-m-bugs, yeylon
Target Milestone: ---Keywords: Regression
Target Release: 3.5.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-23 06:27:58 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
logs none

Description Nikolai Sednev 2014-10-22 16:30:32 UTC
Created attachment 949492 [details]
logs

Description of problem:
Failed to power off VM "VM1-strass". 

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


How reproducible:
100%

Steps to Reproduce:
1.Deploy HE environment on at least 2 hosts.
2.Attach ISO domain and NFS SD.
3.Create VM without any disk, which will start itself from ISO domain, using ISO image of stress linux.
4.Define VM to be ran from one of two hosts hard-coded.
5.Start VM and run stress on it, to get to 100% CPU load for that VM.
6.Migrate VM from its host to another host and then migrate it back again.
7.Try to power-off VM, you won't succeed.


Actual results:
VM which had been asked to powered off, fails to get to that state with error message "Failed to power off VM VM1-strass" .

Expected results:
VM should power-off immediately.

Additional info:
I also noticed that on my HE environment for some reason was shown that on second host was 2 VMs running, although only HE's VM was actually running on it, the second VM was possibly due to the fact that VM-strass migrated there and then returned back, so system for some reason still thinks that VM is running there...

logs attached.

Comment 1 Omer Frenkel 2014-10-23 06:27:58 UTC

*** This bug has been marked as a duplicate of bug 1152973 ***