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.
Descriptionmxie@redhat.com
2017-03-06 13:39:15 UTC
Created attachment 1260408[details]
screenshot
Description of problem:
Should rename network name of rhv in virt-v2v man page
Version-Release number of selected component (if applicable):
virt-v2v-1.36.1-1.el7.x86_64
libguestfs-1.36.1-1.el7.x86_64
RHVM: 4.1.1.2-0.1.el7
How reproducible:
100%
Steps to Reproduce:
1.Check the network name of rhv in virt-v2v man page
# man virt-v2v |grep rhvm
-o rhv -os rhv.nfs:/export_domain --network rhvm
Guest network interface(s) are connected to the target network called "rhvm".
-o rhv -os rhv.nfs:/export_domain --network rhvm
To map a specific network to a target network, for example "default" on the source to "rhvm" on the
virt-v2v [...] --network default:rhvm
virt-v2v [...] --network rhvm
2.Because the network name of rhvm has been changed to ovirtmgmt since rhvm3.6.10,pls refer to screenshot, so need to update the network name of rhv from rhvm to ovirtmgmt in virt-v2v man page
Actual results:
As above description
Expected results:
Change network name of rhv from rhvm to ovirtmgmt in virt-v2v man page
Additional info:
Verify the bug with builds:
virt-v2v-1.36.2-1.el7.x86_64
libguestfs-1.36.2-1.el7.x86_64
Steps:
1.Check the network name of rhv in virt-v2v man page
# man virt-v2v |grep rhvm
nothing
# man virt-v2v |grep ovirtmgmt
-o rhv -os rhv.nfs:/export_domain --network ovirtmgmt
Guest network interface(s) are connected to the target network called "ovirtmgmt".
-o rhv -os rhv.nfs:/export_domain --network ovirtmgmt
To map a specific network to a target network, for example "default" on the source to "ovirtmgmt" on
virt-v2v [...] --network default:ovirtmgmt
virt-v2v [...] --network ovirtmgmt
According to above result, virt-v2v man page has changed network name of rhv from rhvm to ovirtmgmt , the bug has been fixed
So move the bug from ON_QA 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/RHBA-2017:2023
Created attachment 1260408 [details] screenshot Description of problem: Should rename network name of rhv in virt-v2v man page Version-Release number of selected component (if applicable): virt-v2v-1.36.1-1.el7.x86_64 libguestfs-1.36.1-1.el7.x86_64 RHVM: 4.1.1.2-0.1.el7 How reproducible: 100% Steps to Reproduce: 1.Check the network name of rhv in virt-v2v man page # man virt-v2v |grep rhvm -o rhv -os rhv.nfs:/export_domain --network rhvm Guest network interface(s) are connected to the target network called "rhvm". -o rhv -os rhv.nfs:/export_domain --network rhvm To map a specific network to a target network, for example "default" on the source to "rhvm" on the virt-v2v [...] --network default:rhvm virt-v2v [...] --network rhvm 2.Because the network name of rhvm has been changed to ovirtmgmt since rhvm3.6.10,pls refer to screenshot, so need to update the network name of rhv from rhvm to ovirtmgmt in virt-v2v man page Actual results: As above description Expected results: Change network name of rhv from rhvm to ovirtmgmt in virt-v2v man page Additional info: