Bug 1149493 - Missing indication for VM migration failed in events pane (although migration failure appears in tasks pane).
Summary: Missing indication for VM migration failed in events pane (although migration...
Keywords:
Status: CLOSED DUPLICATE of bug 1145636
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Arik
QA Contact: Nisim Simsolo
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-05 12:39 UTC by Nisim Simsolo
Modified: 2014-10-13 07:31 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-13 07:31:09 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Engine log and hosts VDSM log (11.88 MB, application/x-gzip)
2014-10-05 12:56 UTC, Nisim Simsolo
no flags Details

Description Nisim Simsolo 2014-10-05 12:39:42 UTC
Description of problem:
 In case of VM migration failure, There is no indication for it in events  
 pane, although there is indication for it in tasks pane.
 
Version-Release number of selected component (if applicable):
 Red Hat Enterprise Virtualization Manager Version: 3.5.0-0.13.beta.el6ev

How reproducible:
 100%

Steps to Reproduce:
1. using RHEVM UI, create 2 hosts with RHEL 6.5 
2. Create new VM
3. Migrate VM to second host (Select Host Automatically radio button)
4. Migrate VM back to first host (Select Host Automatically radio button)

Actual results:
 First migration succeeded and second migration failed.
 Observing events pane does not show any indication for this failure.
 Observing tasks pane shows "Migrating VM vm1" executing failure.

Expected results:
 An appropriate message should appear in events pane for indicating VM 
 migration failure.

Additional info:
- Engine log and vdsm.log of both hosts attached.
- First migration failure occured around 2014-Oct-05 13:40 and the second one 
  around 2014-Oct-05, 13:48
- According to VDSM log: Thread-7061::ERROR::2014-10-05 
  13:49:28,329::migration::259::vm.Vm::(run) vmId=`d6f0923d-3da7-4286-    
  b8c2-2b9e476e464e`::Failed to migrate 
  Traceback (most recent call last):
  File "/usr/share/vdsm/virt/migration.py", line 245, in run
  self._startUnderlyingMigration(time.time())
  File "/usr/share/vdsm/virt/migration.py", line 284, in 
  _startUnderlyingMigration
    response['status']['message'])
  RuntimeError: migration destination error: Error creating the requested VM

Comment 1 Nisim Simsolo 2014-10-05 12:56:12 UTC
Created attachment 944039 [details]
Engine log and hosts VDSM log

Comment 2 Michal Skrivanek 2014-10-10 17:09:13 UTC
Why is it failing?

Comment 3 Nisim Simsolo 2014-10-12 08:52:51 UTC
(In reply to Michal Skrivanek from comment #2)
> Why is it failing?

Same reason as bug #1145636:
The vm start process failed, KeyError: 'iface'

Comment 4 Vinzenz Feenstra [evilissimo] 2014-10-13 07:31:09 UTC
It is a duplicate of bug #1145636

There's the same thing going on here.

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


Note You need to log in before you can comment on or make changes to this bug.