Bug 1614748 - Progress is incorrectly reported when transport method is SSH
Summary: Progress is incorrectly reported when transport method is SSH
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-ansible-collection
Classification: oVirt
Component: v2v-conversion-host
Version: 1.1.10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.2.6
: ---
Assignee: Tomáš Golembiovský
QA Contact: Yadnyawalk Tale
URL:
Whiteboard:
Depends On:
Blocks: 1614790
TreeView+ depends on / blocked
 
Reported: 2018-08-10 10:38 UTC by Fabien Dupont
Modified: 2018-09-04 06:30 UTC (History)
2 users (show)

Fixed In Version: ovirt-ansible-v2v-conversion-host-1.6.1-1.el7ev
Clone Of:
Environment:
Last Closed: 2018-09-04 06:30:53 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.2?
tgolembi: planning_ack?
rule-engine: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)

Description Fabien Dupont 2018-08-10 10:38:59 UTC 
Description of problem:
When calling virt-v2v-wrapper.py with SSH as the transport method, the progress is not correctly reported. The state file reports progress on the wrong file name:

{"started"=>true, "disks"=>[{"path"=>"[datastore12] test_migration/test_migration-flat", "progress"=>71.54}, {"path"=>"[datastore12] test_migration/test_migration.vmdk", "progress"=>0}], "pid"=>59814, "disk_count"=>1}

The expected output is:

{"started"=>true, "disks"=>[{"path"=>"[datastore12] test_migration/test_migration.vmdk", "progress"=>0}], "pid"=>59814, "disk_count"=>1}


Version-Release number of selected component (if applicable): 1.6.0-1


How reproducible: Always


Steps to Reproduce: Run a migration with SSH transport method.
Comment 1 Fabien Dupont 2018-08-10 10:40:20 UTC 
Related commits:
- https://github.com/oVirt/ovirt-ansible-v2v-conversion-host/commit/299569ed4c2c2977f8f3b9e29230a0b7475809ca
- https://github.com/oVirt/ovirt-ansible-v2v-conversion-host/commit/cdbba193abc690965cc3b0b6a45fec58b8df4e94
Comment 2 Tomáš Golembiovský 2018-08-13 06:06:59 UTC 
ovirt-ansible-v2v-conversion-host-1.6.1-1.el7ev
Comment 3 Yadnyawalk Tale 2018-09-03 16:57:51 UTC 
Verified with CFME's v2v plugin, I can successfully migrate vm with transport method is SSH.

Following wrapper.log shows backend v2v-virt-wrapper working correctly with patch.
 
2018-09-03 09:03:01,440:DEBUG: Initializing disk list from [u'[NFS_Datastore_1] 67-ytale-thomas-disk-virt/67-ytale-thomas-disk-virt.vmdk'] (virt-v2v-wrapper:886)
2018-09-03 09:03:01,440:DEBUG: Internal disk list: [{'path': '[NFS_Datastore_1] 67-ytale-thomas-disk-virt/67-ytale-thomas-disk-virt.vmdk', 'progress': 0}] (virt-v2v-wrapper:894)


Verified on: 

CFME - 5.9.4.7.20180829201904_ced41ae
RHV - 4.2.6.4
virt-v2v-wrapper - 1.6.3-1.el7ev
Comment 5 Tomáš Golembiovský 2018-09-03 20:32:18 UTC 
Thanks Yadnyawalk. This looks OK.
Note You need to log in before you can comment on or make changes to this bug.