Hide Forgot
Description of problem: In case of corrupted ovf (VM/template) in export domain, access to the ovf list generate exception in the code. This exception is NOT sent to the engine log. Version-Release number of selected component (if applicable): is25 How reproducible: 100% Steps to Reproduce: 1. Have corrupted ovf vm/template in export domain 2. Go to export domain OR, Refresh export domain OR, Import / Export VM from/to export domain. Additional info: The event message, generated in this case: "Failed to read VM '[Empty Name]' OVF, it may be corrupted" There is a separate bug (#1036635) regarding this event.
i dont understand, you complain the code caught the exception (how do you know there is an exception if its not logged?) and logged a nice error in the audit log? it is not clear what is the issue here, please elaborate, what is missing/what did you expect? please also attach relevant engine.log
Following the exception event, looking in the engine.log, showed no error. rgolan found in the code, that the exception is NOT sent to the engine.log. For this purpose I opened this bug.
In current master and I see a log entry in engine.log. 2013-12-18 10:28:07,935 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (http--0.0.0.0-8080-1) Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Failed to read VM '[Unknown name]' OVF, it may be corrupted
we could improve the engine.log with the exception message, as it may provide some more info on the error.
Verified on av7: I've corrupted an ovf of a vm in export VM, by deleting several chars from it. and when doing refresh of the export domain VM list, generate these engine.log messages: 014-04-30 15:55:03,311 ERROR [org.ovirt.engine.core.utils.ovf.OvfParser] (ajp-/127.0.0.1:8702-4) Failed Parsing OVF due to A pseudo attribute name is expected. 2014-04-30 15:55:03,318 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp-/127.0.0.1:8702-4) Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Failed to read VM '[Empty Name]' OVF, it may be corrupted
Closing as part of 3.4.0
What was the resolution here?
Adding needinfo flag for rgolan to answer comment # 7
why is this NEW again?
(In reply to Richard W.M. Jones from comment #7) > What was the resolution here? In case your question refer to verification, it was verified that the Exception for corrupted ovf in export domain, is INDEED sent to engine log.
Fair enough. However the underlying bug (that there is no useful information in the exception) is not fixed.