So how does one determine if there is an issue open or not? And how do they get
This issue makes SSSD unusable in our production environment. We may have to look at
running without SSSD in the short term, if that is possible on SLES 12.
I'm not quite understanding why this error does not show up all the time. How do two
entries with the same GID get into the cache?
For our case, say we have a set of groups abcd..1, abcd..2 etc, all with the same GID. I
would expect the first lookup (e.g. abcd..1) to put an entry in the cache. If there is
then a lookup by GID, (getent group <GID>) it would return this entry. However a
lookup by name (e.g. abcd..2) would have to query LDAP, right? Then what happens, does
this new data overwrite the old GID entry in the cache? Or is there some bug whereby
sometimes a duplicate entry gets made? Why is there a check for duplicates when a GID is
looked up as opposed to when an entry is placed in the cache?
Is there any kind of workaround for this? e.g. is there a way to exclude specific GIDs
from being placed in the cache? This would make for inefficient lookups as they would have
to hit the LDAP server, but it is a small percentage of the total number of groups.