Hide Forgot
Description of problem: Please change event message: "Failed to read VM '[Empty Name]' OVF, it may be corrupted", to be more clear. For example, by adding the ovf file name/s. This way user will be able to identify which ovfs are corrupted. 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.
this bug won't fit into 3.5 release and is being deferred to a later release. If you deeply care about this bug and deserves to be re-evaluated please let me know
Yes, please fix this bug. It affects virt-v2v, and makes it impossible for us to debug problems with the OVF we are generating.
Hi Richard, what exactly are you missing that can make debugging easier? the message this bug talks about is the message in the ui event log, you always have the detailed info in the engine.log also, the ovf file name is not reported to the engine, only the content, as a string, so if its corrupted and we couldn't extract the name, we might not be able to get anything from it (it can also be a garbage string, nothing to show the user) if we really think that in this case the name of the file would be helpful, a bigger change would be required. i'm not sure what we can do for 3.5 anyway.
(In reply to Omer Frenkel from comment #3) > Hi Richard, what exactly are you missing that can make debugging easier? > the message this bug talks about is the message in the ui event log, you > always have the detailed info in the engine.log Since writing the comment, we did find engine.log which has more detail (although it's a lot harder for users to find it). It would be good to push the complete reason why the parsed failed (ie. the lowest level error messages) all the way up to the RHEV-M logs, and this applies in other areas too. The name of the OVF file doesn't really matter for virt-v2v, since we already know that. At the moment, our OVF files are correct and parsable, so this is not so much of a problem.
Thank you, in that case i'm re-targeting for 3.6, adding the failure msg does make sense, and probably do-able.
Verified on rhevm 3.6.0-15: Corrupted Template brings this event: Failed to read Template '[Empty Name]' OVF, it may be corrupted. Underlying error message: The markup in the document preceding the root element must be well-formed. Corrupted Template brings this event: Failed to read VM '[Empty Name]' OVF, it may be corrupted. Underlying error message: The markup in the document preceding the root element must be well-formed.