Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 996610
Description of problem: Sssd initial enumeration sometimes has no effect if an attempt to list groups is made right after starting sssd. I.e. "getent group" output doesn't include groups managed by sssd at least up to 30 seconds after the start, if the first attempt was made within about 0.1s after the start. If at least about half a second delay is introduced before first attempt, the groups appear in "getent group" output. Version-Release number of selected component (if applicable): python-sssdconfig-1.11.0-0.1.beta2.el7.noarch sssd-krb5-common-1.11.0-0.1.beta2.el7.x86_64 sssd-krb5-1.11.0-0.1.beta2.el7.x86_64 libsss_idmap-1.11.0-0.1.beta2.el7.x86_64 libipa_hbac-1.11.0-0.1.beta2.el7.x86_64 sssd-common-1.11.0-0.1.beta2.el7.x86_64 sssd-ldap-1.11.0-0.1.beta2.el7.x86_64 sssd-ad-1.11.0-0.1.beta2.el7.x86_64 sssd-proxy-1.11.0-0.1.beta2.el7.x86_64 sssd-client-1.11.0-0.1.beta2.el7.x86_64 sssd-ipa-1.11.0-0.1.beta2.el7.x86_64 sssd-1.11.0-0.1.beta2.el7.x86_64 How reproducible: Within 50 attempts Steps to Reproduce: Modify the attached "init_enum_failure_test" script to suit local setup and execute it as root. Actual results: The script outputs "Group enumeration not retrieved within 5 attempts", exits with status 1. Expected results: The script produces no output, exits with status 0.
Fields changed
blockedby: => blocking: => changelog: => coverity: => design: => design_review: => 0 feature_milestone: => fedora_test_page: => milestone: NEEDS_TRIAGE => SSSD 1.11.1 priority: major => blocker review: True => 0 selected: => testsupdated: => 0
milestone: SSSD 1.11.1 => NEEDS_TRIAGE
milestone: NEEDS_TRIAGE => SSSD 1.13 beta
mark: => 0
priority: blocker => major
Enumeration is not the default and actively discouraged.
priority: major => minor
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
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)
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/3107
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.