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.

Bug 1579780

Summary: After updating to RHEL 7.5 failing to clear the sssd cache [rhel-7.5.z]
Product: Red Hat Enterprise Linux 7 Reporter: Oneata Mircea Teodor <toneata>
Component: sssdAssignee: SSSD Maintainers <sssd-maint>
Status: CLOSED ERRATA QA Contact: sssd-qe <sssd-qe>
Severity: high Docs Contact:
Priority: high    
Version: 7.5CC: aheverle, daniele, dconsoli, fidencio, gparente, grajaiya, jhrozek, jstephen, lmanasko, lslebodn, mkosek, mupadhye, mzidek, pbrezina, sgoveas, tscherf, vvasilev
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: sssd-1.16.0-19.el7_5.3 Doc Type: Bug Fix
Doc Text:
Previously, an RPM macro that is supposed to restart SSSD after an upgrade was placed into a section where the condition that enables this scriptlet was never true. As a consequence, the sssd service did not restart automatically during the upgrade from 7.4 to 7.5. With this update, the sssd service is now restarted explicitly instead of using the macro that was previously used. As a result, the sssd service now restarts after an upgrade.
 Story Points: ---
Clone Of: 1565774 Environment:
Last Closed: 2018-06-26 16:49:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1565774    
Bug Blocks:    

Description Oneata Mircea Teodor 2018-05-18 10:23:47 UTC 
This bug has been copied from bug #1565774 and has been proposed to be backported to 7.5 z-stream (EUS).
Comment 3 Madhuri 2018-06-05 11:04:58 UTC 
Reproducing the issue:
1) Configuring sssd client with 389 directory server.

# rpm -qa sssd
sssd-1.15.2-50.el7.x86_64

# systemctl -ojson status sssd
● sssd.service - System Security Services Daemon
   Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/sssd.service.d
           └─journal.conf
   Active: active (running) since Tue 2018-06-05 02:19:25 EDT; 2min 14s ago
 Main PID: 30128 (sssd)
   CGroup: /system.slice/sssd.service
           ├─30128 /usr/sbin/sssd -i -f
           ├─30129 /usr/libexec/sssd/sssd_be --domain LDAP --uid 0 --gid 0 --debug-to-files
           ├─30130 /usr/libexec/sssd/sssd_nss --uid 0 --gid 0 --debug-to-files
           └─30131 /usr/libexec/sssd/sssd_pam --uid 0 --gid 0 --debug-to-files

2) Update the sssd to sssd-1.16.0-19.el7.x86_64

from log, 
Jun 05 02:33:24 Updated: sssd-client-1.16.0-19.el7.x86_64
Jun 05 02:33:25 Updated: python-sssdconfig-1.16.0-19.el7.noarch
Jun 05 02:33:26 Updated: sssd-common-1.16.0-19.el7.x86_64
Jun 05 02:33:26 Updated: sssd-krb5-common-1.16.0-19.el7.x86_64
Jun 05 02:33:27 Updated: sssd-common-pac-1.16.0-19.el7.x86_64
Jun 05 02:33:27 Updated: sssd-ipa-1.16.0-19.el7.x86_64
Jun 05 02:33:27 Updated: sssd-ad-1.16.0-19.el7.x86_64
Jun 05 02:33:28 Updated: sssd-krb5-1.16.0-19.el7.x86_64
Jun 05 02:33:28 Updated: sssd-ldap-1.16.0-19.el7.x86_64
Jun 05 02:33:28 Updated: sssd-proxy-1.16.0-19.el7.x86_64
Jun 05 02:33:28 Updated: sssd-1.16.0-19.el7.x86_64

3) Check pid of sssd after upgrade,
# service sssd status
Redirecting to /bin/systemctl status sssd.service
● sssd.service - System Security Services Daemon
   Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2018-06-05 02:19:25 EDT; 14min ago
 Main PID: 30128 (sssd)
   CGroup: /system.slice/sssd.service
           ├─30128 /usr/sbin/sssd -i -f
           ├─30129 /usr/libexec/sssd/sssd_be --domain LDAP --uid 0 --gid 0 --debug-to-files
           ├─30130 /usr/libexec/sssd/sssd_nss --uid 0 --gid 0 --debug-to-files
           └─30131 /usr/libexec/sssd/sssd_pam --uid 0 --gid 0 –debug-to-files

pid of sssd did not change after upgrade.

4) Clear its cache via "sss_cache -E".  
[root@cloud-qe-07 ~]# sss_cache -E
(Tue Jun  5 02:34:03:138387 2018) [sss_cache] [sysdb_domain_cache_connect] (0x0010): DB version too old [0.18], expected [0.20] for domain LDAP!
Higher version of database is expected!
In order to upgrade the database, you must run SSSD.
Removing cache files in /var/lib/sss/db should fix the issue, but note that removing cache files will also remove all of your cached credentials.
Could not open available domains

[root@cloud-qe-07 ~]# rpm -qa sssd
sssd-1.16.0-19.el7.x86_64

the above steps reproduced the issue. 

5) Now upgrading sssd to sssd-1.16.0-19.el7_5.5.x86_64

after update:
from log,
Jun 05 02:53:40 Updated: sssd-client-1.16.0-19.el7_5.5.x86_64
Jun 05 02:53:42 Updated: sssd-common-1.16.0-19.el7_5.5.x86_64
Jun 05 02:53:42 Updated: sssd-krb5-common-1.16.0-19.el7_5.5.x86_64
Jun 05 02:53:42 Updated: sssd-common-pac-1.16.0-19.el7_5.5.x86_64
Jun 05 02:53:43 Updated: sssd-ad-1.16.0-19.el7_5.5.x86_64
Jun 05 02:53:43 Updated: sssd-ldap-1.16.0-19.el7_5.5.x86_64
Jun 05 02:53:44 Updated: sssd-krb5-1.16.0-19.el7_5.5.x86_64
Jun 05 02:53:44 Updated: sssd-proxy-1.16.0-19.el7_5.5.x86_64
Jun 05 02:53:44 Updated: python-sssdconfig-1.16.0-19.el7_5.5.noarch
Jun 05 02:53:45 Updated: sssd-ipa-1.16.0-19.el7_5.5.x86_64
Jun 05 02:53:45 Updated: sssd-1.16.0-19.el7_5.5.x86_64

# rpm -qa sssd
sssd-1.16.0-19.el7_5.5.x86_64

6) check pid
# systemctl -ojson status sssd
● sssd.service - System Security Services Daemon
   Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2018-06-05 02:53:51 EDT; 16min ago
 Main PID: 30842 (sssd)
   CGroup: /system.slice/sssd.service
           ├─30842 /usr/sbin/sssd -i --logger=files
           ├─30843 /usr/libexec/sssd/sssd_be --domain LDAP --uid 0 --gid 0 --logger=files
           ├─30844 /usr/libexec/sssd/sssd_nss --uid 0 --gid 0 --logger=files
           └─30845 /usr/libexec/sssd/sssd_pam --uid 0 --gid 0 --logger=files

pid of sssd changed

7) Clear its cache via "sss_cache -E".
Successfully clear cache using # sss_cache -E without any errors. 


8) check user lookup,
# getent passwd testuser@LDAP
testuser@LDAP:*:14583101:14564100:testuser User:/:/bin/bash
# id testuser@LDAP
uid=14583101(testuser@LDAP) gid=14564100 groups=14564100


From above steps marking as verified.
Comment 7 errata-xmlrpc 2018-06-26 16:49:19 UTC 
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/RHBA-2018:1986