Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1350465 - [RFE] Store detailed log of virt-v2v when importing VM
Summary: [RFE] Store detailed log of virt-v2v when importing VM
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: RFEs
Version: 4.18.15
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.1.0-alpha
: 4.19.2
Assignee: Tomáš Golembiovský
QA Contact: Nisim Simsolo
URL:
Whiteboard:
: 1354176 (view as bug list)
Depends On: 1416112
Blocks: 1430240
TreeView+ depends on / blocked
 
Reported: 2016-06-27 14:09 UTC by Tomáš Golembiovský
Modified: 2017-03-08 06:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Previously, when importing a Virtual Machine, if the import failed, the output of the virt-v2v tool was not available for investigating the reason for the failure, and the import had to be reproduced manually. In this release, the output of virt-v2v is now stored in the /var/log/vdsm/import directory. All logs older than 30 days are automatically removed.
Clone Of:
Environment:
Last Closed: 2017-02-15 14:52:14 UTC
oVirt Team: Virt
Embargoed:
michal.skrivanek: ovirt-4.1?
nsimsolo: testing_plan_complete+
rule-engine: planning_ack?
michal.skrivanek: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 59834 0 master MERGED v2v: Log detailed output of virt-v2v 2020-04-05 13:06:58 UTC
oVirt gerrit 62092 0 master MERGED v2v: Add helper that redirects stdin/out/err 2020-04-05 13:06:58 UTC
oVirt gerrit 62093 0 master MERGED v2v: Bump version requirement on python-cpopen. 2020-04-05 13:06:58 UTC
oVirt gerrit 62094 0 master MERGED v2v: Add PipelineProc, pipeline wrapper object 2020-04-05 13:06:58 UTC

Description Tomáš Golembiovský 2016-06-27 14:09:46 UTC 
oVirt relies on virt-v2v when importing machines from VMware or Xen hypervisor. However, there is currently no way to get the output of virt-v2v from the import. Detailed log of virt-v2v (with the -v -x options added) is often essential when investigating import failures.

Virt-v2v should be always run with the '-v -x' arguments and the output should be stored in a file to be accessible on the VDSM host.
Comment 1 Red Hat Bugzilla Rules Engine 2016-06-27 14:12:04 UTC 
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
Comment 2 Michal Skrivanek 2016-07-11 06:45:50 UTC 
*** Bug 1354176 has been marked as a duplicate of this bug. ***
Comment 3 Sandro Bonazzola 2016-12-12 13:55:52 UTC 
The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified.
Comment 4 Nisim Simsolo 2017-02-07 15:24:25 UTC 
Verification builds: 
ovirt-engine-4.1.0.4-0.1.el7
libvirt-client-2.0.0-10.el7_3.4.x86_64
vdsm-4.19.4-1.el7ev.x86_64
qemu-kvm-rhev-2.6.0-28.el7_3.3.x86_64
sanlock-3.4.0-1.el7.x86_64
virt-v2v-1.32.7-3.el7_3.2.x86_64

Test cases added to external trackers.
Note You need to log in before you can comment on or make changes to this bug.