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.
Created attachment 587579[details]
6 network devices detected, but only 2 checked.
Description of problem:
In virt-p2v client, sometimes the some network devices were not checked as default, especially the network device which connected to p2v server.
There are two reasons for why network device should be checked as default.
1. All the device detected in "Fixed Storage" and "Removable Media" have been checked as default. For consistent behaviour, the network device should be checked as default.
2. Customer could manually un-check any device as he want, but p2v-client could not make the decision. It will take a little trouble if there is no network device in converted guest.(If only one network device, usually it would be un-checked.)
Version-Release number of selected component (if applicable):
virt-p2v-0.8.6-5.20120502.1.el6.iso
virt-v2v-0.8.7-6.el6.x86_64
libguestfs-1.16.19-1.el6.x86_64
libvirt-0.9.10-20.el6.x86_64
augeas-0.9.0-4.el6.x86_64
febootstrap-3.12-1.el6.x86_64
hivex-1.3.3-4.el6.x86_64
libguestfs-winsupport-1.0-7.el6.x86_64
virtio-win-1.5.1-1.el6.noarch
How reproducible:
70%
Steps to Reproduce:
1. Host launch a p2v client with pxe boot method.
2. Start to convert, then check if network device have been checked in "Network Interface" pane?
Actual Results:
If there is a few network device, only some of them have been checked.
If there is only one network device, usually the network device was not checked status.
Expected results:
All the network device should be checked as default consistently.
Comment 2RHEL Program Management
2012-12-14 07:06:26 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 4Richard W.M. Jones
2015-03-12 17:06:27 UTC
I'm closing this bug:
- virt-p2v has been rewritten for RHEL 7.2
- Unofficial previews of the new version are available:
http://oirase.annexia.org/virt-p2v/
- If a similar bug occurs with the new version of virt-p2v,
please open a new bug against Red Hat Enterprise Linux 7 / libguestfs
Created attachment 587579 [details] 6 network devices detected, but only 2 checked. Description of problem: In virt-p2v client, sometimes the some network devices were not checked as default, especially the network device which connected to p2v server. There are two reasons for why network device should be checked as default. 1. All the device detected in "Fixed Storage" and "Removable Media" have been checked as default. For consistent behaviour, the network device should be checked as default. 2. Customer could manually un-check any device as he want, but p2v-client could not make the decision. It will take a little trouble if there is no network device in converted guest.(If only one network device, usually it would be un-checked.) Version-Release number of selected component (if applicable): virt-p2v-0.8.6-5.20120502.1.el6.iso virt-v2v-0.8.7-6.el6.x86_64 libguestfs-1.16.19-1.el6.x86_64 libvirt-0.9.10-20.el6.x86_64 augeas-0.9.0-4.el6.x86_64 febootstrap-3.12-1.el6.x86_64 hivex-1.3.3-4.el6.x86_64 libguestfs-winsupport-1.0-7.el6.x86_64 virtio-win-1.5.1-1.el6.noarch How reproducible: 70% Steps to Reproduce: 1. Host launch a p2v client with pxe boot method. 2. Start to convert, then check if network device have been checked in "Network Interface" pane? Actual Results: If there is a few network device, only some of them have been checked. If there is only one network device, usually the network device was not checked status. Expected results: All the network device should be checked as default consistently.