Learn more about these different git repos.
Other Git URLs
https://bugzilla.redhat.com/show_bug.cgi?id=891281 (Red Hat Enterprise Linux 6)
Description of problem: When using sssd to serve maps for automounter it sometimes happen that certain maps are not 'seen'. I observe this behavior with large maps (~100 keys): [root@logind yum.repos.d]# automount -m | grep 'orlaj' [root@logind yum.repos.d]# automount -m | grep 'orlaj' [root@logind yum.repos.d]# automount -m | grep 'orlaj' orlaj | belfast:/vol/users/users/& But the requested key is in the cache: [root@logind yum.repos.d]# ldb3search -H /var/lib/sss/db/cache_default.ldb -b cn=autofsmaps,cn=custom,cn=default,cn=sysdb | grep orl no symbol `init_samba_module' found in /usr/lib64/ldb/memberof.so: /usr/lib64/ldb/memberof.so: undefined symbol: init_samba_module WARNING: Module [memberof] not found asq: Unable to register control with rootdse! dn: name=orlajbelfast:/vol/users/users/&,name=auto.home,cn=autofsmaps,cn=custom ,cn=default,cn=sysdb automountKey: orlaj name: orlajbelfast:/vol/users/users/& distinguishedName: name=orlajbelfast:/vol/users/users/&,name=auto.home,cn=auto Version-Release number of selected component (if applicable): sssd-1.9.2-6.upstream_1_9_3.el6_3.x86_64 How reproducible: run 'automount -m' command a couple of times and look for missing keys. Quite easily reproducible. Steps to Reproduce: 1. configure sssd&autofs to serve maps for automounter 2. run 'automount -m' a couple of times 3. Actual results: output of the command 'automount -m' is not consistent Expected results: 'automount -m' should always return the same result
Fields changed
blockedby: => blocking: => coverity: => design: => design_review: => 0 feature_milestone: => fedora_test_page: => milestone: NEEDS_TRIAGE => SSSD 1.9.5 selected: => testsupdated: => 0
owner: somebody => pbrezina
patch: 0 => 1
resolution: => fixed status: new => closed
Metadata Update from @dpal: - Issue assigned to pbrezina - Issue set to the milestone: SSSD 1.9.5
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/2781
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.