Bug 719838

Summary: error : virNetTLSContextLoadCredentials:162 : Unable to set x509 key and certificate
Product: Red Hat Enterprise Linux 6 Reporter: Nan Zhang <nzhang>
Component: libvirtAssignee: Daniel Veillard <veillard>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 6.2CC: berrange, dallan, dnaori, dyuan, iheim, mshao, rwu, veillard, whuang
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: libvirt-0.9.3-2.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 11:16:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
libvirtd log none

Description Nan Zhang 2011-07-08 06:31:07 UTC 
Description of problem:
as subject.

Version-Release number of selected component (if applicable):
libvirt-0.9.3-1.el6.x86_64
vdsm-4.9-71.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. yum install vdsm. 
2. yum install rhevm.
3. start vdsmd service. 
  
Actual results:
06:44:49.801: 3650: error : virNetTLSContextLoadCredentials:162 : Unable to set x509 key and certificate: /etc/pki/vdsm/certs/vdsmcert.pem, /etc/pki/vdsm/keys/vdsmkey.pem: Base64 unexpected header error.

Expected results:
it should be works well.

Additional info:
Comment 5 Daniel Berrangé 2011-07-08 10:16:49 UTC 
The order of the key/cert parameters was reversed in one case. This only affected people overriding the default locations for certs in libvirtd.conf

http://www.redhat.com/archives/libvir-list/2011-July/msg00413.html
Comment 7 David Naori 2011-07-11 19:27:23 UTC 
Verified.
libvirt-0.9.3-2.el6 
vdsm-4.9-81.el6.x86_64
Comment 8 errata-xmlrpc 2011-12-06 11:16:06 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.

http://rhn.redhat.com/errata/RHBA-2011-1513.html