Bug 690189 - 2.2.z - Guest will be left in migrating from status, even if the guest on destination died or inaccessible
Summary: 2.2.z - Guest will be left in migrating from status, even if the guest on des...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: vdsm22
Version: 5.6
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Dan Kenigsberg
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
: 697279 (view as bug list)
Depends On:
Blocks: 729319
TreeView+ depends on / blocked
 
Reported: 2011-03-23 14:35 UTC by Vladik Romanovsky
Modified: 2018-11-14 13:47 UTC (History)
14 users (show)

Fixed In Version: vdsm22-4.5-65.el5
Doc Type: Bug Fix
Doc Text:
If migrating a virtual machine from one host to another failed, the virtual machine was locked on the Red Hat Enterprise Linux Manager server until the timeout limit was reached. Now, if a virtual machine migration fails, the migration is cancelled and the virtual machine remains on the original host.
Clone Of:
Environment:
Last Closed: 2012-02-21 04:52:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
suggest patch by Vladik (3.31 KB, patch)
2011-03-24 23:38 UTC, Dan Kenigsberg 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 725368 0 high CLOSED VDSM: During failed migration, VM stops responding for ~20 minutes 2021-02-22 00:41:40 UTC
Red Hat Knowledge Base (Legacy) 54495 0 None None None Never
Red Hat Product Errata RHBA-2012:0169 0 normal SHIPPED_LIVE vdsm bug fix update 2012-02-21 09:51:13 UTC

Internal Links: 725368

Description Vladik Romanovsky 2011-03-23 14:35:24 UTC 
Currently, there is no treatment on a source, in case the VM on destination fails, during migration.

According to BZ: 654937, comments 9 and 12, Qemu will not fail the migration, in this case.

Due to the above, the migration on the source will remain stuck, until the timeout exceeds. This can be a very long time, while during this time, the VM will be locked on the RHEV-M server.

Moreover, the migration should be canceled and not left in active, after the timeout exceeds.


Steps to Reproduce:
1. Create a VM with 10G memory and 
2. increase memory load on it 
3. kill or block the destination vm 



Thanks,

Vladik
Comment 1 Dan Kenigsberg 2011-03-24 23:38:42 UTC 
Created attachment 487438 [details]
suggest patch by Vladik
Comment 3 Yaniv Kaul 2011-04-17 12:40:25 UTC 
*** Bug 697279 has been marked as a duplicate of this bug. ***
Comment 4 Yaniv Kaul 2011-04-17 12:41:35 UTC 
(In reply to comment #3)
> *** Bug 697279 has been marked as a duplicate of this bug. ***

QE has hit this in the master setup as well (see above duplicate).
Comment 5 Dan Kenigsberg 2011-07-19 21:33:00 UTC 
Patch series ending based on Vladik's code was posted at http://gerrit.usersys.redhat.com/691
Comment 6 Vladik Romanovsky 2011-07-21 11:29:11 UTC 
Verification steps:

1. Create a VM with ~4G memory 
2. to ensure that the migration will take some time, increase the memory / cpu
usage on it (I used 7zip for windows)
3. start a migration
4. during the migration, destroy the destination or block the network
connection  
   to the destination host 

Expected result:
 - Migration should be canceled
Comment 8 Daniel Paikov 2011-07-24 13:22:46 UTC 
Checked on 4.5-65. However, migration takes 20 minutes and during this time the VM is stuck in Not Responding status.
Comment 10 Kate Grainger 2011-08-24 04:25:30 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
If migrating a virtual machine from one host to another failed, the virtual machine was locked on the Red Hat Enterprise Linux Manager server until the timeout limit was reached. Now, if a virtual machine migration fails, the migration is cancelled and the virtual machine remains on the original host.
Comment 12 errata-xmlrpc 2012-02-21 04:52:37 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0169.html
Note You need to log in before you can comment on or make changes to this bug.