Learn more about these different git repos.
Other Git URLs
https://bugzilla.redhat.com/show_bug.cgi?id=878419 (Red Hat Enterprise Linux 6)
Description of problem: sss_userdel doesn't remove entries from in-memory cache Version-Release number of selected component (if applicable): 1.9.2-24 How reproducible: Always Steps to Reproduce: 1. Configure sssd for local provider. domain section in sssd.conf [domain/LOCAL] id_provider = local 2. Add a user # sss_useradd -u 1000 -h /home/user1000 -s /bin/bash user1000 3. Lookup the user # getent passwd user1000 user1000:*:1000:1000:user1000:/home/user1000:/bin/bash 4. Delete the user # sss_userdel user1000 5. Lookup the user again # getent passwd user1000 user1000:*:1000:1000:user1000:/home/user1000:/bin/bash Actual results: User lookup returns the deleted user. This is due to in-memory cache. ldbsearch shows that the user is deleted from ldb cache. Expected results: User/Group deletion should delete them both from ldb and in-memory cache Additional info:
Fields changed
blockedby: => blocking: => coverity: => design: => design_review: => 0 feature_milestone: => fedora_test_page: => owner: somebody => mzidek patch: 0 => 1 status: new => assigned testsupdated: => 0
milestone: NEEDS_TRIAGE => SSSD 1.9.4 priority: major => minor
milestone: SSSD 1.9.4 => NEEDS_TRIAGE patch: 1 => 0 priority: minor => major
milestone: NEEDS_TRIAGE => SSSD 1.9.4
patch: 0 => 1
resolution: => fixed status: assigned => closed
resolution: fixed => selected: => status: closed => reopened
Reopening. Our QE found that the previous fix didn't handle FQDNs.
The FQDN fix:
resolution: => fixed status: reopened => closed
Metadata Update from @pbrezina: - Issue assigned to mzidek - Issue set to the milestone: SSSD 1.9.4
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/2701
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.
Log in to comment on this ticket.