Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1345743 - SASL authentication failed to create client context when connecting to libvirt daemon
SASL authentication failed to create client context when connecting to libvir...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt (Show other bugs)
7.3
x86_64 Linux
high Severity high
: rc
: ---
Assigned To: Ján Tomko
Virtualization Bugs
: Regression, TestBlocker
: 1346371 (view as bug list)
Depends On:
Blocks: 1344890
  Show dependency treegraph
 
Reported: 2016-06-13 02:24 EDT by Dan Zheng
Modified: 2016-11-03 14:46 EDT (History)
11 users (show)

See Also:
Fixed In Version: libvirt-2.0.0-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-11-03 14:46:50 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2577 normal SHIPPED_LIVE Moderate: libvirt security, bug fix, and enhancement update 2016-11-03 08:07:06 EDT

  None (edit)
Description Dan Zheng 2016-06-13 02:24:54 EDT
Description of problem:
SASL authentication failed to create client context. It does not happened with libvirt-1.3.4-1.el7.x86_64


Version-Release number of selected component:
libvirt-1.3.5-1.el7.x86_64
qemu-kvm-rhev-2.6.0-5.el7.x86_64
kernel-3.10.0-349.el7.x86_64

How reproducible:
100%

Steps to reproduce:
1. add auth_unix_rw="sasl" in the /etc/libvirt/libvirtd.conf
   add sasl user:
  #echo redhat | saslpasswd2 -p -a libvirt redhat

2. add auth.conf file in the /etc/libvirtd/
# cat /etc/libvirt/auth.conf
[credentials-sasl]
authname=test
password=redhat123
[auth-libvirt-localhost]
credentials=sasl

3. restart libvirtd
systemctl restart libvirtd

4. run virsh cmd
# virsh  -c qemu+unix:///system list
error: failed to connect to the hypervisor
error: authentication failed: Failed to create SASL client context: -7 (invalid parameter supplied)
----------------------------------------------------

Actual results:
See step 4.

Expected results:
Can succeed to connect libvirt daemon.

Additional information:
Comment 2 Han Han 2016-06-16 06:30:07 EDT
The bug blocks vdsm being registered to RHEVM
Comment 4 Ján Tomko 2016-06-20 08:13:02 EDT
*** Bug 1346371 has been marked as a duplicate of this bug. ***
Comment 5 Ján Tomko 2016-06-20 10:33:25 EDT
Upstream patches:
https://www.redhat.com/archives/libvir-list/2016-June/msg01272.html
Comment 6 Ján Tomko 2016-06-23 16:43:41 EDT
Pushed as:
commit 0f7eeb20ad92962f7d2fbf113bfde67b9abe2e44
Author:     Ján Tomko <jtomko@redhat.com>
CommitDate: 2016-06-23 22:15:06 +0200

    Revert "virnetsocket: Provide socket address format in a more standard form"

git describe: v1.3.5-415-g0f7eeb2
Comment 8 yafu 2016-07-25 05:51:03 EDT
Reproduced with libvirt-1.3.5-1.el7.x86_64.
steps:
1.Add auth_unix_rw="sasl" in the /etc/libvirt/libvirtd.conf
   add sasl user:
  #echo redhat | saslpasswd2 -p -a libvirt redhat

2.Restart libvirtd service:
 #systemctl restart libvirtd

3.#virsh -c qemu+unix:///system
 error: failed to connect to the hypervisor
error: authentication failed: Failed to create SASL client context: -7 (invalid parameter supplied)


Verify pass with libvirt-2.0.0-3.el7.x86_64.
1.Do the step1-2 in the reproduced steps;

2.#virsh -c qemu+unix:///system
Please enter your authentication name: redhat
Please enter your password: 
Welcome to virsh, the virtualization interactive terminal.

Type:  'help' for help with commands
       'quit' to quit

virsh # 

  
3.Also pass with auth_tcp = "sasl" and auth_tls = "sasl" setting.
Comment 10 errata-xmlrpc 2016-11-03 14:46:50 EDT
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/RHSA-2016-2577.html

Note You need to log in before you can comment on or make changes to this bug.