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.
Bug 1609618 - Can NOT restart network in guest after converting aacraid-win2012r2 host to rhv by virt-p2v
Summary: Can NOT restart network in guest after converting aacraid-win2012r2 host to r...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virt-v2v
Version: 9.1
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Richard W.M. Jones
QA Contact: tingting zheng
URL:
Whiteboard: P2V
Depends On: 2038105
Blocks: 1872297
TreeView+ depends on / blocked
 
Reported: 2018-07-30 03:32 UTC by mxie@redhat.com
Modified: 2022-05-30 02:29 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-09 15:30:19 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
virt-p2v-aacraid-win2012r2-rhev.zip (101.96 KB, application/zip)
2018-07-30 03:32 UTC, mxie@redhat.com 		no flags Details
aacraid-restart-network-rhv.png (159.33 KB, image/png)
2018-07-30 03:35 UTC, mxie@redhat.com 		no flags Details
View All

Description mxie@redhat.com 2018-07-30 03:32:49 UTC 
Created attachment 1471410 [details]
virt-p2v-aacraid-win2012r2-rhev.zip

Description of problem:
Can NOT restart network in guest after converting aacraid-win2012r2 host to rhv by virt-p2v

Version-Release number of selected component (if applicable):
virt-v2v-1.38.2-9.el7.x86_64
libguestfs-1.38.2-9.el7.x86_64
libvirt-4.5.0-4.el7.x86_64
qemu-kvm-rhev-2.12.0-8.el7.x86_64
virt-p2v-1.38.2-2.el7.iso
rhv:4.2.5-0.1.el7ev


How reproducible:
100%

Steps to Reproduce:
1.Install win2012r2 on accraid host
2.Boot host into virt-p2v client
3.Input conversion server info and pass the test connection
4 Input conversion info ,then start convert
5.The conversion could be finished without error,import guest from export domain to data domain on rhv
6.Check points on guest, guest can get ip but cannot restart network, pls refer to screenshot "aacraid-restart-network-rhv" and log "virt-p2v-aacraid-win2012r2-rhev"


Actual results:
As above description

Expected results:
Can restart network in guest after converting aacraid-win2012r2 host to rhv by virt-p2v

Additional info:
1.Can restart network in win2012r2 host before p2v conversion
2.Network driver can't be installed automatically if convert aacraid-win2012r2 host to libvirt by virt-p2v due to bug1595688, but can restart network successfully after installing network driver manually
Comment 2 mxie@redhat.com 2018-07-30 03:35:26 UTC 
Created attachment 1471411 [details]
aacraid-restart-network-rhv.png
Comment 3 mxie@redhat.com 2018-07-30 06:29:14 UTC 
Sorry, need to correct the reproduce steps of the bug as below and add another additional info

Steps to Reproduce:
1.Install win2012r2 on accraid host
2.Boot host into virt-p2v client
3.Input conversion server info and pass the test connection
4 Input conversion info ,then start conversion
5.The conversion could be finished without error,import guest from export domain to data domain on rhv
6.Due to bug1609614, don't set ovirtmgmt bridge for guest's network and power on guest
7. After powering on guest successfully, then set ovirtmgmt bridge in guest network
8.Check points on win2012-accraid guest, guest can get ip but cannot restart network, pls refer to screenshot "aacraid-restart-network-rhv" and log "virt-p2v-aacraid-win2012r2-rhev"



Additional info
Network has IP and can restart network successfully in  MD-rhel7.5 guest after p2v converting MD-rhel7.5 host to rhv4.2
Comment 4 Richard W.M. Jones 2018-08-09 07:31:24 UTC 
> 7. After powering on guest successfully, then set ovirtmgmt bridge in guest network

I'm not sure I understand what this means.  Is it a RHV setting?
If so then it's likely to be a RHV bug of some sort.  However in
general terms changing the guest's network configuration underneath
it isn't likely to work well so it's not really surprising that it
fails.
Comment 5 Jaroslav Suchanek 2019-12-04 15:30:45 UTC 
This bug will be addressed in next major release.
Comment 9 RHEL Program Management 2021-02-15 07:41:03 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 10 Richard W.M. Jones 2021-02-15 09:09:35 UTC 
I'm sorry, this bug was closed in error by the "stale bugs" process.
Comment 11 John Ferlan 2021-09-08 19:05:15 UTC 
Bulk update: Move RHEL-AV bugs to RHEL8.
Comment 13 RHEL Program Management 2021-12-31 07:27:00 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 14 Richard W.M. Jones 2021-12-31 09:15:47 UTC 
I have to apologise - this bug was closed in error by a process we have no
control over which closes bugs claiming they are "stale" when they are not.
We have tried to have this process removed, with no success.  I am reopening
it and setting the "stale" date far into the future.
Comment 15 Richard W.M. Jones 2022-04-26 12:36:00 UTC 
Just checking through remaining RHEL 8 / virt-v2v bugs, and this one came up.

As this bug doesn't affect customers, we ought to either close it or move it
to RHEL 9.  mxie, do you happen to know if this bug still affects virt-v2v?
If so, could you move it to RHEL 9 please?

If it's either not reproducible or you no longer have the environment to
reproduce it, then I suggest closing it.
Comment 16 mxie@redhat.com 2022-04-28 07:10:18 UTC 
(In reply to Richard W.M. Jones from comment #15)
> Just checking through remaining RHEL 8 / virt-v2v bugs, and this one came up.
> 
> As this bug doesn't affect customers, we ought to either close it or move it
> to RHEL 9.  mxie, do you happen to know if this bug still affects virt-v2v?
> If so, could you move it to RHEL 9 please?
> 
> If it's either not reproducible or you no longer have the environment to
> reproduce it, then I suggest closing it.

Because the server which has accraid storage controller has problem and IT is fixing it, I would like to move the bug to RHEL 9 first, I will reproduce the bug when the server is repaired
Note You need to log in before you can comment on or make changes to this bug.