Description of problem: Minor log issue of virt-v2v Version-Release number of selected component (if applicable): virt-v2v-1.38.2-10.el7.x86_64 How reproducible: 100% Steps to Reproduce: [stderr] virt-v2v: error: transfer of disk 2/1 failed, see earlier error messages Actual results: [stderr] virt-v2v: error: transfer of disk 2/1 failed, see earlier error messages Expected results: It should be 'disk 1/1'. [stderr] virt-v2v: error: transfer of disk 1/1 failed, see earlier error messages Additional info:
Sorry I had a fix for this already this morning but I got side-tracked: https://www.redhat.com/archives/libguestfs/2018-August/msg00127.html
Fixed upstream with https://github.com/libguestfs/libguestfs/commit/90c9c12258fbb9a89d16f798725d16fe5bb3504c which is in libguestfs >= 1.39.9.
I can find the error info in below automatic job of virt-v2v rhv-upload conversion Job run with virt-v2v-1.38.2-10 : https://libvirt-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/v2v-RHEL-7.6-runtest-x86_64-matrix-kvm_ISCSI_rhv_upload/1/testReport/rhev/convert_vm_to_ovirt/kvm_windows_win2008r2_arch_x86_64_raw_f_ISCSI_rhv_upload_rhv_direct_rhv_verifypeer_preallocated/ But I can't reproduce the bug by manual v2v rhv-upload conversion, so rerun the above the job with virt-v2v-1.38.2-11.el7.x86_64, all cased are passed without the error of bug, so I think the bug could be verified Job rerun with virt-v2v-1.38.2-11:https://libvirt-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/v2v-RHEL-7.6-runtest-x86_64-matrix-kvm_ISCSI_rhv_upload/2/testReport/rhev/convert_vm_to_ovirt/
You can try trigger more than one job at one time or trigger all rhv-upload jobs to increase the load and pressure of ovirt server, then rhv-upload may fail and then you can check the log and verify it.
(In reply to xiaodwan from comment #6) > You can try trigger more than one job at one time or trigger all rhv-upload > jobs to increase the load and pressure of ovirt server, then rhv-upload may > fail and then you can check the log and verify it. I have trigger all rhv-upload jobs at the same time, but there is still no case failed with same error of bug,could you please help to try?
The auto jobs still cannot reproduce it. Since it's a minor log issue and no functional problem, i think we can move to verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:3021