Description of problem:
It is a regression of bz678410 and bz894381. Observed automation failures on all archs. Memory cache is not updated after user is deleted from ldap server.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. # id puser1
uid=2001(puser1) gid=2001 groups=2001
2. Delete puser1 from ldap server
3. # ssh -l puser1 localhost
Permission denied, please try again.
4. # id puser1
uid=2001(puser1) gid=2001 groups=2001 <== Should not work
ldbsearch shows that the user still exists in cache, even after the entry_negative_timeout.
User should also be removed from cache.
No need to mark QE-reported bugs as private.
Thank you for reporting the bug, though.
* master: 9fc96a4a2b07b92585b02dba161ab1eb2dbdad98
* sssd-1-12: d0d6956c3748ba670448edd548b8edd37c5f5c1a
Verified the bug on SSSD Version: sssd-1.12.4-47.el6
Successful execution of the automation suite verifies this bug. See the results from testcase: "bz678410-and-bz894381-id-command-shows-recently-deleted-users" on beaker job https://beaker.engineering.redhat.com/jobs/990732.
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.