Bug 1054994 - Provide more info on failing migration error
Summary: Provide more info on failing migration error
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-webadmin
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.4.0
Assignee: bugs@ovirt.org
QA Contact: bugs@ovirt.org
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-17 22:05 UTC by Meital Bourvine
Modified: 2014-06-18 08:42 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-27 10:09:53 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)
vdsm log - source (3.50 KB, text/x-log)
2014-01-17 22:05 UTC, Meital Bourvine
no flags Details

Description Meital Bourvine 2014-01-17 22:05:01 UTC
Created attachment 851830 [details]
vdsm log - source

Description of problem:
On failing migration, the user gets a non descriptive error, for example:

Migration started (VM: nophpapp01, Source: novmnode1, Destination: novmnode2, User: edgarsm).
Migration failed due to Error: Fatal error during migration. Trying to migrate to another Host (VM: nophpapp01, Source: novmnode1, Destination: novmnode2).
Migration failed due to Error: Fatal error during migration (VM: nophpapp01, Source: novmnode1, Destination: novmnode2).

How reproducible:
100%

Actual results:
The user can't understand the reason for the failure.

Expected results:
The user will get a message that will help him debug the problem.

Comment 1 Michal Skrivanek 2014-02-27 10:09:53 UTC
I don't think seeing "libvirtError: Failed to inquire lock: No such process" in the UI would make it any more clear….
maybe we can add something generic like "check vdms, libvirt and qemu logs"…but that's about it.


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