Bug 1252772
Summary: | [RFE][virt-v2v] When there is a failure to import a VM using virt-v2v oVirt does not seem to reflect the error from VDSM | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Maor <mlipchuk> | ||||||
Component: | RFEs | Assignee: | Arik <ahadas> | ||||||
Status: | CLOSED DEFERRED | QA Contact: | Nisim Simsolo <nsimsolo> | ||||||
Severity: | low | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | --- | CC: | bugs, lsurette, lsvaty, michal.skrivanek, mtessun, rbalakri, rjones, srevivo, ykaul | ||||||
Target Milestone: | --- | Keywords: | FutureFeature | ||||||
Target Release: | --- | Flags: | ylavi:
ovirt-future?
ylavi: planning_ack? ylavi: devel_ack? ylavi: testing_ack? |
||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Enhancement | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2018-07-06 15:27:05 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Maor
2015-08-12 08:50:58 UTC
Created attachment 1061884 [details]
vdsm
(In reply to Maor from comment #0) There is no need to enable debugging in virt-v2v for that, we get errors that happen in the middle of the conversion without debugging mode. Note that we parse the output of virt-v2v. So we get the description of errors from virt-v2v as text, therefore we decide not to show it in the audit log. So audit log only shows that the conversion failed and to see why you should look for it in the engine/vdsm log. I believe that if we ever change the API with virt-v2v to be based on codes for errors instead of getting it as text, then we will be able to map codes to presentable messages in audit logs. According to c#2 there seems to be a reasonable way for getting these errors. |