Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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:
Pushed as:
commit 0f7eeb20ad92962f7d2fbf113bfde67b9abe2e44
Author: Ján Tomko <jtomko>
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
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.
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