#2303 Sssd fails to refresh nested groups correctly
Closed: Invalid None Opened 10 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 995031

Created attachment 784330
nested_refresh_test

Description of problem:
Sssd fails to properly reflect changes to LDAP directory containing rfc2307bis
nested groups.

Version-Release number of selected component (if applicable):
sssd-common-1.11.0-0.2.beta2.el7.x86_64
sssd-ad-1.11.0-0.2.beta2.el7.x86_64
python-sssdconfig-1.11.0-0.2.beta2.el7.noarch
sssd-client-1.11.0-0.2.beta2.el7.x86_64
sssd-krb5-common-1.11.0-0.2.beta2.el7.x86_64
sssd-ldap-1.11.0-0.2.beta2.el7.x86_64
sssd-proxy-1.11.0-0.2.beta2.el7.x86_64
sssd-ipa-1.11.0-0.2.beta2.el7.x86_64
sssd-1.11.0-0.2.beta2.el7.x86_64
libsss_idmap-1.11.0-0.2.beta2.el7.x86_64
sssd-krb5-1.11.0-0.2.beta2.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
Modify the attached nested_refresh_test script to suit local setup and execute
it as root.

Actual results:
uid=10000(user10000) gid=10001(user10000)
groups=10001(user10000),10000(group10000)
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
uid=10000(user10000) gid=10001 groups=10001
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023

Expected results:
uid=10000(user10000) gid=10001(user10000)
groups=10001(user10000),10000(group10000)
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
uid=10000(user10000) gid=10002(user10000)
groups=10002(user10000),10000(group10000),10001(group10001)
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023

Additional info:

NOTE: This reproduces on RHEL6 with sssd 1.9.2-82.7 as well.

If the first directory change is not done, the remaining second change is
reflected correctly.

If a 10 minute delay is introduced between changing the directory and
retrieving the user information, the second line becomes this:

uid=10000(user10000) gid=10002(user10000)
groups=10002(user10000),10001(group10001)
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023

Which is still incorrect, though.

Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
milestone: NEEDS_TRIAGE => SSSD 1.13 beta
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

mark: => 0

Fields changed

milestone: SSSD 1.13 beta => SSSD 1.13 backlog
priority: major => minor

Mass-moving tickets not planned for the next two releases.

Please reply with a comment if you disagree about the move..

milestone: SSSD 1.13 backlog => SSSD 1.15 beta

Suggest to close, I don't think anyone was able to reproduce this issue ever since.

review: 0 => 1
selected: => Not need
sensitive: => 0

We couldn't reproduce the issue since it was initially reported, therefore I'm closing the ticket.

resolution: => worksforme
status: new => closed

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD Future releases (no date set yet)

7 years ago

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/3345

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata