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 1174200 - New virt-v2v failure: CURL: Error opening file: NSS: client certificate not found (nickname not specified): Invalid argument
Summary: New virt-v2v failure: CURL: Error opening file: NSS: client certificate not f...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libguestfs
Version: 7.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: 7.1
Assignee: Richard W.M. Jones
QA Contact: Virtualization Bugs
URL:
Whiteboard: V2V
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-15 11:27 UTC by Sokratis
Modified: 2015-11-19 06:58 UTC (History)
6 users (show)

Fixed In Version: libguestfs-1.28.1-1.24.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 06:58:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
virt-v2v debug log (4.11 KB, text/plain)
2014-12-15 11:34 UTC, Sokratis 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2183 0 normal SHIPPED_LIVE libguestfs bug fix and enhancement update 2015-11-19 08:18:42 UTC

Description Sokratis 2014-12-15 11:27:53 UTC 
Description of problem:

When running latest virt-v2v (virt-v2v-1.28.1-1.17.el7.x86_64) the following error is thrown:

CURL: Error opening file: NSS: client certificate not found (nickname not specified): Invalid argument


Additional info:

The cookie is retrieved successfully from vCenter Server and the error is thrown when running qemu-img command.
Comment 1 Sokratis 2014-12-15 11:34:40 UTC 
Created attachment 968906 [details]
virt-v2v debug log
Comment 2 Richard W.M. Jones 2014-12-15 12:00:51 UTC 
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 ...
Comment 3 Richard W.M. Jones 2014-12-15 12:02:50 UTC 
You could also try the tips here.  If anything helps, please let us know.

https://rcritten.fedorapeople.org/nss_compat_ossl.html
Comment 5 Sokratis 2014-12-15 14:14:02 UTC 
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.
Comment 7 Richard W.M. Jones 2015-04-13 11:02:11 UTC 
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
Comment 9 zhoujunqin 2015-05-11 07:17:21 UTC 
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.
Comment 10 Sokratis 2015-05-21 12:23:05 UTC 
I can confirm the above for virt-v2v-1.28.1-1.36.el7.x86_64.
Comment 12 errata-xmlrpc 2015-11-19 06:58:21 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.