Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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:
Comment 2Richard W.M. Jones
2018-08-14 13:41:34 UTC
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?
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