Bug 1318922
| Summary: | network name mangling after virt-v2v conversion causes old-style network scripts to fail | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | keanli <keanli> | ||||||||||||
| Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> | ||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||
| Priority: | medium | ||||||||||||||
| Version: | 7.3 | CC: | bthurber, jsuchane, kkulkarn, mxie, mzhan, ptoscano, rjones, smallamp, tzheng, xiaodwan | ||||||||||||
| Target Milestone: | rc | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | x86_64 | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | V2V | ||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | |||||||||||||||
| : | 1642021 (view as bug list) | Environment: | |||||||||||||
| Last Closed: | 2019-06-25 13:11:57 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: | |||||||||||||||
| Bug Blocks: | 1473046, 1558351, 1642021 | ||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
keanli
2016-03-18 07:16:16 UTC
By the way, the log file isn't complete. I think you didn't use both the -v and -x options, or else you didn't collect stdout & stderr. Anyway, the problem here is obviously to do with the network interface getting renamed from ens192 to eth0. The corresponding /etc/sysconfig/network-scripts/ifcfg-ens192 file should therefore be renamed. However predicting how systemd/udev/the kernel is going to mangle network names at boot is a tricky one. Out of development time for RHEL 7.4. Moving to RHEL 7.5. Description of problem: There is no IP in RHEL7.3 guest after converting from source target "vmware/kvm" by virt-v2v Version-Release number of selected component (if applicable): virt-v2v-1.36.3-4.el7.x86_64 libguestfs-1.36.3-4.el7.x86_64 qemu-kvm-1.5.3-139.el7.x86_64 libvirt-3.2.0-7.el7.x86_64 How reproducible: 100% Steps to Reproduce: Scenario1: 1.Convert rhel7.3 guest from vmware to rhv by virt-v2v # virt-v2v -ic vpx://root.75.182/data/10.73.3.19/?no_verify=1 esx5.5-rhel7.3-x86_64 -o rhev -os 10.73.131.93:/home/nfs_export --password-file /tmp/passwd -b ovirtmgmt -n ovirtmgmt -v -x |& tee > virt-v2v-esx-rhel7.3.log 2.After finishing conversion, import rhe7.3 guest from export domain to data domain 3.Power on the guest and found eth0 can't obtain IP, pls refer to screenshot"vmware-rhel7.3-rhv" and log"virt-v2v-esx-rhel7.3.log" Scenario2: 1.Convert rhel7.3 guest from kvm to rhv by virt-v2v 2.After finishing conversion, import rhe7.3 guest from export domain to data domain 3.Power on the guest and found eth0 can't obtain IP Scenario3: 1.Convert rhel7.2 guest from vmware to rhv by virt-v2v # virt-v2v -ic vpx://root.75.182/data/10.73.3.19/?no_verify=1 esx5.5-rhel7.2-x86_64 -o rhev -os 10.73.131.93:/home/nfs_export --password-file /tmp/passwd -b ovirtmgmt -n ovirtmgmt -v -x |& tee > virt-v2v-esx-rhel7.2.log 2.After finishing conversion, import rhe7.2 guest from export domain to data domain 3.Power on the guest and found eth0 can obtain IP, pls refer to screenshot"vmware-rhel7.2-rhv" and and log"virt-v2v-esx-rhel7.2.log" Actual results: Although there is existing bug1318922 result in the rhel7 guest can't restart network service successfully, rhel7.2 still could obtain ip after converting by virt-v2v as scenario3,so it is not normal that rhel7.3 guest can't obtain IP after converting from source target "vmware/kvm" by virt-v2v Expected results: There is IP in RHEL7.3 guest after converting from source target "vmware/kvm" by virt-v2v Additional info: 1.RHEL7.3 guest can obtain IP after converting from source target "xen" by virt-v2v because original rhel7.3 guest's network name is eth0 on xen server Hi Pino, Due to above problem, all the rhel7.3 guests are failed in virt-v2v full matrix auto testing,Although I'm not sure whether above problem is duplicate with this bug,it is obvious that this problem will be fixed if bug1318922 could fixed, so the bug has blocked some tests, could you help to fix this bug if you have time? Created attachment 1284337 [details]
vmware-rhel7.2-rhv
Created attachment 1284338 [details]
vmware-rhel7.3-rhv
Created attachment 1284339 [details]
virt-v2v-esx-rhel7.2.log
Created attachment 1284340 [details]
virt-v2v-esx-rhel7.3.log
With below builds and convert openSUSE OS from ESX exist network problem,add the comment here to verify when the bug fixed. virt-v2v-1.36.6-1.el7.x86_64 libguestfs-1.36.6-1.el7.x86_64 libvirt-3.7.0-2.el7.x86_64 qemu-kvm-rhev-2.9.0-16.el7_4.8.x86_64 Steps: Scenario 1: 1.Prepare a openSUSE x84_64 guest on ESX server. 2.Using virt-v2 to convert the guest to rhv # virt-v2v -ic vpx://root.75.182/data/10.73.72.61/?no_verify=1 esx6.0-opensuse13.2-x86_64 --password-file /tmp/passwd -o rhv -os 10.73.131.93:/home/nfs_export Scenario 2: 1.Prepare a openSUSE x84_64 guest on ESX server. 2.Using virt-v2 to convert the guest to libvirt # virt-v2v -ic vpx://root.75.182/data/10.73.72.61/?no_verify=1 esx6.0-opensuse13.2-x86_64 --password-file /tmp/passwd I am hitting this issue while running V2V migrations using CloudForms. Network names change on migrated VM compared to source VM. This issue will be addressed in next major release of RHEL. |