| Summary: | connect to hypervisor with unconfigured tls/tcp connection reports wrong message | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | weizhang <weizhan> |
| Component: | libvirt | Assignee: | Gunannan Ren <gren> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.2 | CC: | dallan, dyuan, gren, mzhan, rwu, veillard, weizhan, whuang, xhu |
| Target Milestone: | rc | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | libvirt-0.9.3-8.el6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-12-06 11:17:00 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
weizhang
2011-07-20 07:24:48 UTC
on version libvirt-0.9.3-5.el6.x86_64 it is right. The patch is intended to solve the problem. https://www.redhat.com/archives/libvir-list/2011-July/msg01325.html commit b14800af14f8c13f2ca80f0a912fbb94d68628e8
Author: Guannan Ren <gren>
Date: Wed Jul 20 15:20:18 2011 +0100
Don't try to close a NULL virNetClientPtr
* src/rpc/virnetclient.c: Skip close attempt if virNetClientPtr
is NULL
I have verified it on RHEL6u2 server with the following component and it passed: libvirt-0.9.3-8.el6 qemu-kvm-0.12.1.2-2.172.el6 kernel-2.6.32-171.el6 The steps are as follows: 1 connect to localhost without tls configuration: # virsh -c qemu+tls:///system error: Cannot read CA certificate '/etc/pki/CA/cacert.pem': No such file or directory error: failed to connect to the hypervisor 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 |