Description of problem: Now v2v will create a tmp dir to save the converting images, after finishing conversion, v2v will move the images in tmp dir to "Image" dir, but fails to geneate OVF file in master/vms/xxxxx dir. Version-Release number of selected component (if applicable): virt-v2v-0.6.0-4.el5 How reproducible: 100% Steps to Reproduce: 1.Run v2v to convert image to RHEV 2.Check whether the converted image existed in "Storage=>export storage=>VM Import" 3.There is nothing in "VM Import" 4. Go to export storage to check there is no OVF file in the correspondent dir: # pwd /rhev/data-center/mnt/10.66.90.115:_vol_v2vwulinglu_wulingluv2v_fcp__export/b0003790-8d93-4b9d-9e11-ddeec00a5b4d/master/vms/22866d5a-f7ca-45f6-81a0-ce82d2c540c0 [root@amd-1352-8-1 22866d5a-f7ca-45f6-81a0-ce82d2c540c0]# ls [root@amd-1352-8-1 22866d5a-f7ca-45f6-81a0-ce82d2c540c0]# Actual results: V2V fails to generate OVF file Expected results: V2V can generate OVF file Additional info: the dir in export storage # ls dom_md images master v2v.vlYGhgC4
in commit : RHEV: Cleanup volumes on unclean shutdown ------------------------------------------------------------------ --- a/lib/Sys/VirtV2V/Target/RHEV.pm +++ b/lib/Sys/VirtV2V/Target/RHEV.pm @@ -669,6 +724,8 @@ EOF dir => $dir, error => $!))); + return Sys::VirtV2V::Target::RHEV::Vol->_move_vols(); + my $vm; my $ovfpath = $dir.'/'.$vmuuid.'.ovf'; open($vm, '>', $ovfpath) ------------------------------------------------------------------ it returns before write ovf file, so ovf file won't be generated.
Fixed in 0.6.0-5.el5
Verified in 0.6.0-5.el5 . Now v2v can generate OVF file to let RHEVM identify the converted guests.
Where can I access 0.6.0-5 version for testing? I have access to the Beta channel but am still on 0.6.0-1
(In reply to comment #7) > Where can I access 0.6.0-5 version for testing? > > I have access to the Beta channel but am still on 0.6.0-1 Unfortunately I don't think it's possible to access these internal builds until they're pushed to RHN (Beta or otherwise). I think the current build is about ready for a push, so hopefully sometime soon.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2010-0495.html