Learn more about these different git repos.
Other Git URLs
we have 2 automount maps. Several entries have the same key in both maps but point to a different mount location. This causes a collision in the sssd database.
A small example:
- /foo/mykey -> server1:/location - /bar/mykey -> server2:/anotherlocation
(mount /foo/mykey) The cache database contains a key:
key = "DN=NAME=mykey,CN=AUTOFSENTRIES,CN=CUSTOM,CN=MYDOMAIN,CN=SYSDB\00" data = "...automountInformation: server1:/location, memberof: name=auto.foo,cn=custom,cn=mydomain...
(mount /bar/mykey) sssd returns "server1:/location" instead of "server2:/anotherlocation". The data in the cache is:
key(70) = "DN=NAME=mykey,CN=AUTOFSENTRIES,CN=CUSTOM,CN=MYDOMAIN,CN=SYSDB\00" data = "...automountInformation: server1:/location, memberof: name=auto.foo,cn=custom,cn=mydomain..., auto.bar,cn=custom,cn=mydomain
This looks like a db design bug. The key should also contain the map the autofs entry belongs to.
Version: Fedora 17 sssd-1.8.4-14.fc17.x86_64
Workaround: disable sssd and use the ldap server directly
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.9.0 rhbz: => 0
owner: somebody => jhrozek status: new => assigned
patch: 0 => 1
Fixed in:
resolution: => fixed status: assigned => closed
Metadata Update from @bramv: - Issue assigned to jhrozek - Issue set to the milestone: SSSD 1.9.0
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/2548
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.
Login to comment on this ticket.