Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1148366

Summary: VMs not migrating following libvirtd stop
Product: Red Hat Enterprise Virtualization Manager Reporter: Ilanit Stein <istein>
Component: ovirt-engineAssignee: Nobody <nobody>
Status: CLOSED NOTABUG QA Contact: Ilanit Stein <istein>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: ecohen, gklein, iheim, istein, lpeer, lsurette, ofrenkel, rbalakri, Rhev-m-bugs, 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-10-07 14:44:06 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
engine.log
none
vdsm log none

Description Ilanit Stein 2014-10-01 09:48:14 UTC 
Description of problem:
VMs running on a host, are not migrated automatically to a 2nd host, that is able to contain them.

Version-Release number of selected component (if applicable):
engine: vt4
hosts (rhel6.6):
libvirt-0.10.2-45.el6.x86_64
vdsm-4.16.5-2.el6ev.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Have 8 vms (from vmpool) running on a host.
2. Run: initctl stop libvirtd => host cannot recover(remain "Non Operational"), and none of the VMs, running on that host, are not migrated.

Actual results:

Expected results:
VMs should be migrated automatically, in case the host is
Comment 1 Ilanit Stein 2014-10-01 10:40:09 UTC 
Created attachment 943012 [details]
engine.log
Comment 2 Ilanit Stein 2014-10-01 10:43:48 UTC 
Created attachment 943013 [details]
vdsm log
Comment 3 Omer Frenkel 2014-10-02 07:18:22 UTC 
what is the cluster's resilience policy?
Comment 4 Ilanit Stein 2014-10-05 05:48:48 UTC 
Migrate Virtual Machines
Comment 5 Omer Frenkel 2014-10-07 14:44:06 UTC 
when host moves to non-operational because of "initializing/recovering from crash", the engine doesnt send the migrate command to it, because it would fail,
in this state, every command sent to vdsm fails with the "initializing/recovering from crash" error.