#2681 SSSD cache is not updated after user is deleted from ldap server
Closed: Fixed None Opened 5 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 1232738

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):
sssd-1.12.4-46.el6

How reproducible:
Always

Steps to Reproduce:
1. # id puser1
uid=2001(puser1) gid=2001 groups=2001

2. Delete puser1 from ldap server

3. # ssh -l puser1 localhost
puser1@localhost's password:
Permission denied, please try again.
puser1@localhost's password:

4. # id puser1
uid=2001(puser1) gid=2001 groups=2001   <== Should not work

Actual results:
ldbsearch shows that the user still exists in cache, even after the
entry_negative_timeout.

Expected results:
User should also be removed from cache.

Additional info:

Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: no => 0
owner: somebody => lslebodn
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12.6

Fields changed

patch: 0 => 1
status: new => assigned

Fields changed

summary: Memory cache is not updated after user is deleted from ldap server => SSSD cache is not updated after user is deleted from ldap server

resolution: => fixed
status: assigned => closed

Metadata Update from @jhrozek:
- Issue assigned to lslebodn
- Issue set to the milestone: SSSD 1.12.6

3 years ago

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/3722

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata