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

Bug 840553

Summary: After VM migration fail, dead lock is reached on the engine.log
Product: Red Hat Enterprise Virtualization Manager Reporter: Ilanit Stein <istein>
Component: ovirt-engineAssignee: mkublin <mkublin>
Status: CLOSED CURRENTRELEASE QA Contact: Ilanit Stein <istein>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.1.0CC: bazulay, dyasny, hateya, iheim, lpeer, mkublin, ohochman, oramraz, Rhev-m-bugs, sgrinber, yeylon, ykaul, yzaslavs
Target Milestone: ---Keywords: Regression
Target Release: ---Flags: istein: needinfo+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt, infra
Fixed In Version: si12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-04 20:05:12 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 of migration source host cinteg16.ci.lab.tlv.redhat.com
none
vdsm log of migration destination host cinteg14.ci.lab.tlv.redhat.com
none
engine log (search for deadlock) none

Description Ilanit Stein 2012-07-16 15:11:58 UTC 
Description of problem:

After VM migration failure (not BZ yet), a dead lock is reached in the engine log.

VM migration: done during VM migration test: 2 up RHEL6.3 hosts, same cluster, run on latest 3.1 setup.
One host is set to maintenance, VM migration fail (probably because of a bug),
and host fail to move to maintenance.  

How reproducible:

Migration failure always reproduced. dead lock was seen only once, because we only have a one run test engine log. before that all test runs did not have engine log. I'll update later on if it is always reproducible, as now engine log generation works OK.




Additional info:

If a bug will be filed for the VM migration failure, I'll attach it's link to this bug.
Comment 1 Ilanit Stein 2012-07-16 15:14:06 UTC 
Created attachment 598479 [details]
vdsm log of migration source host cinteg16.ci.lab.tlv.redhat.com
Comment 2 Ilanit Stein 2012-07-16 15:17:07 UTC 
Created attachment 598480 [details]
vdsm log of migration destination host cinteg14.ci.lab.tlv.redhat.com
Comment 4 Ilanit Stein 2012-07-17 07:24:57 UTC 
regression keyword removed as it is not for certain.
Comment 5 Ilanit Stein 2012-07-22 08:31:28 UTC 
Created attachment 599572 [details]
engine log (search for deadlock)
Comment 6 mkublin 2012-07-22 09:21:31 UTC 
These is a same problem that inside an internal bug , because of I am already working on it , I am taking these and close internal as duplicate
Comment 7 mkublin 2012-07-22 09:22:12 UTC 
*** Bug 840463 has been marked as a duplicate of this bug. ***
Comment 9 mkublin 2012-07-24 12:53:58 UTC 
http://gerrit.ovirt.org/#/c/6568/
Comment 10 Yair Zaslavsky 2012-07-24 12:59:12 UTC 
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=4137b7774db49ab117f609d0e8a2a2bdc76224eb
Comment 11 Ilanit Stein 2012-08-08 13:01:18 UTC 
Verified on latest: last commit:  21ceff466539a742ec968326b01ed9053f0d0a6a

I've repruduced the same vm migration failure, that used to cause deadlock before.
and deadlock didn't happen.
Comment 13 Ilanit Stein 2012-08-09 07:14:10 UTC 
No official release. As mentioned above, it was tested on latest backend.