RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/1846

Lukas found that depending on the order we save groups to cache, we might fail to save cyclic group memberships correctly. With a setup like this:

{{{
   ________
   |  CG1 |------------>sssduser1
   |______|<---+
      |        |
      |        |
      |     ________
      +---->|  CG2 |--->sssduser2
            |______|

}}}

Then depending on whether CG1 or CG2 is requested first, then only sssduser1 or only sssduser2 may be returned.

The logs would show an EEXIST situation from memberof plugin.

Fixed upstream:

master: aab77886be61d915805bf16500e06fab6a5a7e4f
sssd-1-10: 716705950986a3221d64aec4274b6e1e73f16121
sssd-1-9: e4c8fd085da8132db082de616675061018fdc5a2

Verified with version sssd-1.9.2-122.el6.x86_64

Output from beaker automation run:
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: BZ 928797 Cyclic group_member_list
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [   PASS   ] :: Running 'groups sssduser1 | grep cg2' (Expected 0, got 0)
:: [   PASS   ] :: Running 'groups sssduser2 | grep cg1' (Expected 0, got 0)
:: [   PASS   ] :: Running 'id sssduser1 | grep cg2' (Expected 0, got 0)
:: [   PASS   ] :: Running 'id sssduser2 | grep cg1' (Expected 0, got 0)
:: [   LOG    ] :: Duration: 1s
:: [   LOG    ] :: Assertions: 4 good, 0 bad
:: [   PASS   ] :: RESULT: BZ 928797 Cyclic group_member_list

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/RHBA-2013-1680.html