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

Bug 1054994

Summary: Provide more info on failing migration error
Product: [Retired] oVirt Reporter: Meital Bourvine <mbourvin>
Component: ovirt-engine-webadminAssignee: bugs <bugs>
Status: CLOSED WONTFIX QA Contact: bugs <bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: acathrow, ecohen, gklein, iheim, mgoldboi, michal.skrivanek, nlevinki, yeylon
Target Milestone: ---   
Target Release: 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-27 10:09:53 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 - source none

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.