Bug 1595365

Summary: [RFE]v2v - Enhanced Error Reporting in UI from virt-v2v logs
Product: Red Hat CloudForms Management Engine Reporter: Kedar Kulkarni <kkulkarn>
Component: V2VAssignee: Brett Thurber <bthurber>
Status: CLOSED CURRENTRELEASE QA Contact: Yadnyawalk Tale <ytale>
Severity: medium Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: medium    
Version: 5.9.0CC: bthurber, fdupont, hkataria, jprause, lavenel, mfeifer, mpovolny, obarenbo, rjones, simaishi, smallamp, sshveta
Target Milestone: GAKeywords: TestOnly, ZStream
Target Release: 5.11.0   
Hardware: All   
OS: All   
Whiteboard: v2v
Fixed In Version: 5.11.0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1693747 (view as bug list) Environment:
Last Closed: 2019-12-13 15:16:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: V2V Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1644399, 1693747    
Attachments:
Description Flags
Status Detail none

Description Kedar Kulkarni 2018-06-26 18:21:03 UTC
Description of problem:
I and Brett(bthurber) were discussing the change in the UI removing the source and target datastore/domain sizes from the infra mappings due to the inaccurate info being returned by the API. 

I relied on it in the past to select the source and target for VM migration.  In the past it would block if the target indicated a smaller free space than the source even though the total size of the VMs selected may be less.

This lead to troubleshooting a failed VM migration which caused by lack of space on the target storage, Brett found this out through the virt-v2v log for the VM. 

Is there a way we could display the failure cause in the UI so the consumer doesn't have to parse a full, verbose log file?  The current pop-up comes to mind.  Something like an informational icon next to the log file with the cause of failure listed in a pop-up. 


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Kedar Kulkarni 2018-10-25 14:42:20 UTC
https://github.com/ManageIQ/manageiq-v2v/issues/734

Comment 3 Fabien Dupont 2019-03-18 16:29:57 UTC
[V2V] Expose virt-v2v-wrapper error message in options hash - https://github.com/ManageIQ/manageiq/pull/18564
[V2V] Expose virt-v2v-wrapper error message in progress.states - https://github.com/ManageIQ/manageiq-content/pull/514

Comment 6 Satoe Imaishi 2019-04-05 17:34:36 UTC
Also: https://github.com/ManageIQ/manageiq-v2v/pull/918

Comment 7 Shveta 2019-05-02 06:25:50 UTC
Created attachment 1561323 [details]
Status Detail

Status Detail shows detail in 5.10.4.1.20190430152139_40a1d86