Learn more about these different git repos.
Other Git URLs
Version 0.12 is installed but 0.11 is linked.
[root@fclient-1120245 ~]# rpm -q libwbclient sssd-libwbclient libwbclient-4.2.3-7.el7.x86_64 sssd-libwbclient-1.13.0-40.el7.x86_64 [root@fclient-1120245 ~]# rpm --scripts -ql sssd-libwbclient postinstall scriptlet (using /bin/sh): /usr/sbin/update-alternatives --install /usr/lib64/libwbclient.so.0.11 \ libwbclient.so.0.11-64 \ /usr/lib64/sssd/modules/libwbclient.so.0.11.0 20 /sbin/ldconfig preuninstall scriptlet (using /bin/sh): if [ $1 -eq 0 ]; then /usr/sbin/update-alternatives --remove \ libwbclient.so.0.11-64 \ /usr/lib64/sssd/modules/libwbclient.so.0.11.0 fi /sbin/ldconfig /usr/lib64/sssd/modules/libwbclient.so.0 /usr/lib64/sssd/modules/libwbclient.so.0.12.0 [root@fclient-1120245 ~]# wbinfo -n SSSDAD2012R2\\Domain\ Users could not obtain winbind interface details: WBC_ERR_WINBIND_NOT_AVAILABLE could not obtain winbind separator! failed to call wbcLookupName: WBC_ERR_WINBIND_NOT_AVAILABLE Could not lookup name SSSDAD2012R2\Domain Users ** Fixed by [root@fclient-1120245 ~]# /usr/sbin/update-alternatives --install /usr/lib64/libwbclient.so.0.12 libwbclient.so.0.12-64 /usr/lib64/sssd/modules/libwbclient.so.0.12.0 20 [root@fclient-1120245 ~]# wbinfo -n SSSDAD2012R2\\Domain\ Users S-1-5-21-988729707-3926255045-3384196396-513 SID_DOM_GROUP (2)
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1273633
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=1273633 1273633]
sssd upstream does not have any libwbclient alternatives. They are used only in downstream (Fedora, el7).
resolution: => invalid status: new => closed
Metadata Update from @steeve: - Issue set to the milestone: NEEDS_TRIAGE
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/3886
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.