Red Hat Bugzilla – Bug 1261951
Improve error message when OVF cannot be parsed from export domain
Last modified: 2016-08-23 16:29:17 EDT
Description of problem: When OVF from the export domain cannot be parsed, the error message is deeply unhelpful. eg: https://bugzilla.redhat.com/show_bug.cgi?id=1261281#c5 "Error parsing OVF due to 2" Even including the stack trace as debug info would massively improve the situation, because we could at least see exactly where in the parser things were failing. Version-Release number of selected component (if applicable): ovirt 3.5 How reproducible: 100% Steps to Reproduce: 1. Export any VM into the export storage domain. 2. Grab the OVF from https://bugzilla.redhat.com/show_bug.cgi?id=1261281#c5 3. Overwrite the VM's OVF in the ESD with the buggy OVF. 4. Go to the Storage -> Export tab 5. You will see an error message about corrupted OVF. 6. In engine.log you'll see the useless error message.
Verified with rhevm-4.0.0.2-0.1.el7ev.noarch according to steps in description. After exporting the vm to export domain I changed the ovf on the ESD, played with several sections according to the attached patch. Error message appears on audit log and engine log e.g.: Failed to read VM '<UNKNOWN>' OVF, it may be corrupted. Underlying error message: OVF error: [Empty Name]: cannot read 'rasd:VirtualQuantity' with value: For input string: "hallo" seems to be the expected result
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-1743.html