Bug 1261951 - Improve error message when OVF cannot be parsed from export domain
Summary: Improve error message when OVF cannot be parsed from export domain
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: unspecified
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-4.0.0-alpha
: 4.0.0
Assignee: Shahar Havivi
QA Contact: sefi litmanovich
Depends On:
TreeView+ depends on / blocked
Reported: 2015-09-10 13:48 UTC by Richard W.M. Jones
Modified: 2016-08-23 20:29 UTC (History)
10 users (show)

Fixed In Version: ovirt 4.0.0 alpha1
Doc Type: Bug Fix
Doc Text:
This update improves the error message written to the log when an OVF from the export domain cannot be parsed. The error message now attempts to pinpoint the problem.
Clone Of:
Last Closed: 2016-08-23 20:29:17 UTC
oVirt Team: Virt
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:1743 0 normal SHIPPED_LIVE Red Hat Virtualization Manager 4.0 GA Enhancement (ovirt-engine) 2016-09-02 21:54:01 UTC
oVirt gerrit 47448 0 master MERGED Improve error message when OVF cannot be parsed from export domain Never

Description Richard W.M. Jones 2015-09-10 13:48:24 UTC
Description of problem:

When OVF from the export domain cannot be parsed, the error
message is deeply unhelpful.  eg:


  "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:


Steps to Reproduce:
1. Export any VM into the export storage domain.
2. Grab the OVF from
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.

Comment 1 sefi litmanovich 2016-06-15 08:41:17 UTC
Verified with rhevm- 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

Comment 3 errata-xmlrpc 2016-08-23 20:29:17 UTC
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.


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