Bug 1174200
| Summary: | New virt-v2v failure: CURL: Error opening file: NSS: client certificate not found (nickname not specified): Invalid argument | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Sokratis <sokratis123k> | ||||
| Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 7.1 | CC: | dyuan, juzhou, mbooth, mzhan, ptoscano, tzheng | ||||
| Target Milestone: | rc | ||||||
| Target Release: | 7.1 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | V2V | ||||||
| Fixed In Version: | libguestfs-1.28.1-1.24.el7 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-11-19 06:58:21 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
Sokratis
2014-12-15 11:27:53 UTC
Created attachment 968906 [details]
virt-v2v debug log
You've got at least: qemu-kvm-rhev-2.1.2-13.el7.x86_64 qemu-img-rhev-2.1.2-13.el7.x86_64 ? This is probably some configuration of vCenter that we've not seen/tested before ... You could also try the tips here. If anything helps, please let us know. https://rcritten.fedorapeople.org/nss_compat_ossl.html It looks like it's related with the vCenter Server version. I got the above error using vCenter Server 4. Using vCenter Server 5, I was able to complete the conversion successfully. I think we should just document that vCenter >= 5 is required. It's certainly the only version I've ever tested. Apparently vCenter 5.0 was released in 2011. The following two commits update the documentation: https://github.com/libguestfs/libguestfs/commit/abf23ece49972111e19147087664e7442d84fdfd https://github.com/libguestfs/libguestfs/commit/e062093881d66b56c4935054ad409ecf2531880b As Comment 7 said, try to reproduce and verify this bug from document side. I can reproduce this issue with package: virt-v2v-1.28.1-1.17.el7.x86_64 libguestfs-1.28.1-1.17.el7.x86_64 steps: 1. Check virt-v2v manual page: # man virt-v2v Result: There is no relating content showing about supported Vcenter server version. Then try to verify with new build: virt-v2v-1.28.1-1.32.el7.x86_64 libguestfs-1.28.1-1.32.el7.x86_64 steps: 1. Check virt-v2v manual page: # man virt-v2v ... INPUT FROM VMWARE VCENTER SERVER Virt-v2v is able to import guests from VMware vCenter Server. vCenter ≥ 5.0 is required. Virt-v2v cannot import guests directly from an ESXi hypervisor. If you don't have vCenter, using OVA is recommended instead (see "INPUT FROM VMWARE OVA" below). Result: Manual page show supporting Vcenter server ≥ 5.0 to user clearly. So move this bug from ON_QA to VERIFIED. I can confirm the above for virt-v2v-1.28.1-1.36.el7.x86_64. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-2183.html |