Red Hat Bugzilla – Bug 881773
mmap cache needs update after db changes
Last modified: 2014-07-23 05:48:21 EDT
This bug is created as a clone of upstream ticket: https://fedorahosted.org/sssd/ticket/1671 In the nested groups case we use the memberof plugin to make changes db-wise for changing memberships, however this means changes are not reflected in the mmap cache until the mmap entry naturally expires and is refreshed. Upon db changes we should make a quick search right after the memberof plugin has done it's work (using modifytimestamp ?) and expire any mmap cache entry that has been chahnged in the db. This will cause th first app that need s the entry to call into sssd and refresh it with proper values.
Verified in version 1.9.2-68 Output from beaker automation run: :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ LOG ] :: 2307bis_011 - bz881773 - mmap cache needs update after db changes :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Stopping sssd: [ OK ] Starting sssd: [ OK ] [ OK ] :: [09:30:06] :: Sleeping for 5 seconds adding new entry "uid=mof_user8,dc=example,dc=com" adding new entry "cn=mofuser8_grp1,dc=example,dc=com" adding new entry "cn=mofuser8_grp2,dc=example,dc=com" 88881 88882 :: [ PASS ] :: Running 'id -G mof_user8 | grep 88881 | grep 88882' adding new entry "cn=mofuser8_grp3,dc=example,dc=com" spawn ssh -q -l mof_user8 localhost echo 'login successful' mof_user8@localhost's password: Could not chdir to home directory /home/mof_user8: No such file or directory login successful :: [ PASS ] :: Authentication successful, as expected :: [ PASS ] :: Running 'auth_success mof_user8 Secret123' 88881 88882 88883 :: [ PASS ] :: Running 'id -G mof_user8 | grep 88881 | grep 88882 | grep 88883' '27ea4a42-a708-4f43-ada4-af1b27e019ca' 2307bis-011-bz881773-mmap-cache-needs-update-after-db-changes result: PASS
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. http://rhn.redhat.com/errata/RHSA-2013-0508.html