Bug 1070649

Summary: HA VM is restarted after manual shutdown from webadmin
Product: Red Hat Enterprise Virtualization Manager Reporter: Julio Entrena Perez <jentrena>
Component: vdsmAssignee: Vinzenz Feenstra [evilissimo] <vfeenstr>
Status: CLOSED DUPLICATE QA Contact: Artyom <alukiano>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.2.0CC: acathrow, bazulay, dfediuck, flo_bugzilla, iheim, lpeer, mavital, michal.skrivanek, ofrenkel, Rhev-m-bugs, sherold, yeylon
Target Milestone: ---Keywords: Reopened
Target Release: 3.4.0   
Hardware: All   
OS: Linux   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-15 10:24:14 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:

Description Julio Entrena Perez 2014-02-27 10:15:07 UTC 
Description of problem:
After shutting down a HA VM and requesting maintenance mode on the host it's running, VM is restarted in other host.

Version-Release number of selected component (if applicable):
rhevm-backend-3.2.5-0.49.el6ev.noarch

How reproducible:
Unknown.

Steps to Reproduce:
1. Shutdown 5 HA VMs from webadmin portal.
2. Immediately afterwards request maintenance mode on the host VMs are running.
3. 

Actual results:
One of the VMs is restarted on another host.

Expected results:
The VM stays shutdown as requested.

Additional info:
Comment 2 Julio Entrena Perez 2014-02-27 10:24:26 UTC 
VM is not running RHEV agent but is running acpid.
Comment 6 Michal Skrivanek 2014-03-31 09:24:46 UTC 

*** This bug has been marked as a duplicate of bug 1073478 ***
Comment 9 Michal Skrivanek 2014-05-15 10:24:14 UTC 
we actually did figure out the root cause for the error just yesterday when the same happened in another case. The exception due to _getBalloonInfo() is indeed addressed by the fix in bug 1073478. 

The resolution of that bug was changed incorrectly, it was ON_QA and can't be reproduced anymore…that doesn't mean CLOSED/INSUFFICIENT_DATA. - I'll fix it there

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