Bug 1033932 - VM stays locked, in being migrated state, even after migration failed.
Summary: VM stays locked, in being migrated state, even after migration failed.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.3.4
Assignee: Arik
QA Contact: Ilanit Stein
URL:
Whiteboard: virt
Depends On:
Blocks: 3.3snap4
TreeView+ depends on / blocked
 
Reported: 2013-11-24 13:28 UTC by Ilanit Stein
Modified: 2019-09-12 07:47 UTC (History)
11 users (show)

Fixed In Version: org.ovirt.engine-root-3.3.0-53
Doc Type: Bug Fix
Doc Text:
A regression that caused virtual machines to remain locked after migration fails has been fixed.
Clone Of:
Environment:
Last Closed: 2014-07-09 11:52:03 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
engine log (515.40 KB, application/x-gzip)
2013-11-24 13:39 UTC, Ilanit Stein 		no flags Details
dest host vdsm log (128.93 KB, application/x-gzip)
2013-11-24 13:40 UTC, Ilanit Stein 		no flags Details
src host vdsm log (953.86 KB, application/x-gzip)
2013-11-24 13:41 UTC, Ilanit Stein 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0863 0 normal SHIPPED_LIVE rhevm 3.3.4 bug fix update 2014-07-09 15:51:43 UTC
oVirt gerrit 21722 0 None None None Never
oVirt gerrit 21723 0 None None None Never
oVirt gerrit 21813 0 None None None Never
oVirt gerrit 21814 0 None None None Never

Description Ilanit Stein 2013-11-24 13:28:38 UTC 
Description of problem:

When there is an error during migration, the vm stays locked. This lock lead to following migration trials failure, on CanDoAction: Cannot ${action} ${type}. VM ${VmName} is being migrated.

service ovirt-engine restart resolve the problem.

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

Steps to Reproduce:
1. Create a problem that will fail migration. (I blocked on destination host storage access iptables -A OUTPUT -d <storage server IP address>  -j DROP
2. Migrate VM (migration is expected to start)
3. Migration VM fail (expected)
4. Fix storage access problem done in 1.
5. Try to migrate VM - and fail, though migrate should succeed.

Additional info:
engine.log error:

2013-11-24 14:14:04,911 WARN  [org.ovirt.engine.core.bll.InternalMigrateVmCommand] (pool-5-thread-41) [eebcd8a] CanDoAction of action InternalMigrateVm failed. Reasons:VAR__ACTION__MIGRATE,VAR__TYPE__VM,ACTION_TYPE_FAILED_VM_IS_BEING_MIGRATED,$VmName test-1
Comment 1 Ilanit Stein 2013-11-24 13:39:43 UTC 
Created attachment 828309 [details]
engine log
Comment 2 Ilanit Stein 2013-11-24 13:40:41 UTC 
Created attachment 828318 [details]
dest host vdsm log
Comment 3 Ilanit Stein 2013-11-24 13:41:36 UTC 
Created attachment 828319 [details]
src host vdsm log
Comment 4 Ilanit Stein 2013-11-25 10:49:24 UTC 
This bug is seen in this test: http://jenkins.qa.lab.tlv.redhat.com:8080/view/Compute/view/3.3-git/view/Virt/job/3.3-git-compute-virt-payloads-rest-nfs/
Comment 6 Arik 2013-12-04 09:14:40 UTC 
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=e25ef61a90a011dc4bae17f2b69a52da606db66a
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=c3e9107d066081d71caba655c02a16238112b963
Comment 7 Ilanit Stein 2013-12-09 10:09:34 UTC 
Verified on is26.

Followed "Steps to Reproduce:" in description.
Comment 8 Itamar Heim 2014-01-21 22:30:33 UTC 
Closing - RHEV 3.3 Released
Comment 9 Itamar Heim 2014-01-21 22:30:33 UTC 
Closing - RHEV 3.3 Released
Comment 10 Itamar Heim 2014-01-21 22:33:34 UTC 
Closing - RHEV 3.3 Released
Comment 11 Michal Skrivanek 2014-06-09 07:45:30 UTC 
we need an additional fix in 3.3.4, note it's already fixed in 3.4 and 3.5/master
Comment 14 Ilanit Stein 2014-06-30 14:23:08 UTC 
Verified on is37 (3.3.4).

Followed "Steps to Reproduce:" in description.
Comment 16 errata-xmlrpc 2014-07-09 11:52:03 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-2014-0863.html
Note You need to log in before you can comment on or make changes to this bug.