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:
https://github.com/ManageIQ/manageiq-v2v/issues/734
[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
Also: https://github.com/ManageIQ/manageiq-v2v/pull/918
Created attachment 1561323 [details] Status Detail Status Detail shows detail in 5.10.4.1.20190430152139_40a1d86