Bug 1609618
| Summary: | Can NOT restart network in guest after converting aacraid-win2012r2 host to rhv by virt-p2v | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | mxie <mxie> | ||||||
| Component: | virt-v2v | Assignee: | Richard W.M. Jones <rjones> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | tingting zheng <tzheng> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 9.1 | CC: | jsuchane, juzhou, lersek, mzhan, ptoscano, rjones, tzheng, xiaodwan | ||||||
| Target Milestone: | rc | Keywords: | Reopened, Triaged | ||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | P2V | ||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2022-05-09 15:30:19 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | 2038105 | ||||||||
| Bug Blocks: | 1872297 | ||||||||
| Attachments: |
|
||||||||
|
Description
mxie@redhat.com
2018-07-30 03:32:49 UTC
Created attachment 1471411 [details]
aacraid-restart-network-rhv.png
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 > 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.
This bug will be addressed in next major release. 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. I'm sorry, this bug was closed in error by the "stale bugs" process. Bulk update: Move RHEL-AV bugs to RHEL8. 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. 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. 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. (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 |