Description of problem: We need to rebase sssd to the latest release of the stable 1.16.x branch to bring in new features and bug fixes Version-Release number of selected component (if applicable): whatever 1.16.x version upstream will have at that time How reproducible: easy Steps to Reproduce: 1. rpm -q sssd 2. 3. Actual results: Expected results: Additional info:
Verified with # rpm -qa sssd sssd-1.16.4-16.el7.x86_64 [root@host-8-246-209 ~]# rpm -qa | grep sssd sssd-krb5-common-1.16.4-16.el7.x86_64 sssd-krb5-1.16.4-16.el7.x86_64 sssd-tools-1.16.4-16.el7.x86_64 sssd-winbind-idmap-1.16.4-16.el7.x86_64 python-sssdconfig-1.16.4-16.el7.noarch sssd-common-pac-1.16.4-16.el7.x86_64 sssd-ldap-1.16.4-16.el7.x86_64 sssd-1.16.4-16.el7.x86_64 sssd-libwbclient-1.16.4-16.el7.x86_64 sssd-ipa-1.16.4-16.el7.x86_64 sssd-proxy-1.16.4-16.el7.x86_64 sssd-kcm-1.16.4-16.el7.x86_64 sssd-client-1.16.4-16.el7.x86_64 sssd-common-1.16.4-16.el7.x86_64 sssd-ad-1.16.4-16.el7.x86_64 sssd-dbus-1.16.4-16.el7.x86_64 Installation and other sanity checks verifies current version of samba. Thus on the basis of above observations, marking the status of bug to 'Verified'.
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://access.redhat.com/errata/RHSA-2019:2177