Bug 1856105
| Summary: | [v2v][VMware to CNV VM import] Any VM import from VMware fails on [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Ilanit Stein <istein> | ||||
| Component: | V2V | Assignee: | Brett Thurber <bthurber> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Ilanit Stein <istein> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 2.4.0 | CC: | cnv-qe-bugs, dagur, ncredi, ptoscano, pvauter, rjones | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-07-16 18:21:30 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: | |||||||
| Attachments: |
|
||||||
|
Description
Ilanit Stein
2020-07-12 18:57:35 UTC
Created attachment 1700744 [details]
kubevirt-v2v-conversion-v2v-rhel7-vm.log
It's quite hard to follow the virt-v2v output but I think the error is (from VDDK): 2020-07-12 18:30:21,529 - root - DEBUG - b'nbdkit: vddk[3]: debug: Cnx_Connect: Error message: Host address lookup for server f02-h26-000-r620.rdu2.scalelab.redhat.com failed: Name or service not known\n' 2020-07-12 18:30:21,529 - root - DEBUG - b'nbdkit: vddk[3]: error: [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: Host address lookup for server f02-h26-000-r620.rdu2.scalelab.redhat.com failed: Name or service not known\n' which would indeed indicate some kind of network problem. I think that is the source ESXi server? since this is a regression, and we do not allow regressions between releases, im setting the target to 2.4 and will suggest blocker On same CNV environment, the VM imports that were failing yesterday, are now in status "off" - That is there was an automatic retry, and they were migrated eventually successfully. Also, I just ran VM import of some other RHEL7 VM successfully. I will try again to run VM import for the same rhel7/win2016 VMs, that were failing before, and update here. Tried again same VMs, and now it's failing for me on the same reported error. Might be that there is a network instability issue here. In CNV UI the status shown is: The virtual machine could not be imported. Terminated with Error (exit code 2). and link to pod logs is provided. opening the pod logs show the failure reported in this bug. If needed I can provide CNv environment details, where problem reproduces. Tested 10 VM imports from VMware to CNV BM, and could not reproduce this bug.
@Brett,
Also managed to import from the Vmware you provided same VM ("fdupont-test-migration (rhel7 with 2 disks) that I could not import on the PSI environment before, from some reason.
Closing this BZ per QE as it wasn't reproducible on a stable env. |