SSSD / sssd

#3486 Improve `enumerate` documentation/troubleshooting guide
Closed: Fixed Opened by fidencio.

Closed: Fixed
Reopen Issue

While the title of the issue is a little bit too generic, the intention behind this report is to add information that when using enumeration we may hit some known issue like missing group information due to the watchdog timeout.

Would be nice to mention that in the sssd.conf man page and also add some info about this in the troubleshooting guide.

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.16.0

Metadata Update from @jhrozek:
- Issue priority set to: minor
- Issue tagged with: docs

Any update on this? We need to use enumerate on some servers and this is somewhat
unstable.

I'm not sure what update do you expect or what issues do you see, but this ticket is only about documenting the current constraints of enumeration (so, discouraging its use), not about any changes in the code.

Since we are required to release a new upstream tarball no later than Friday Oct-20, I'm moving tickets that will not be closed by that date to the next milestone, 1.16.1

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.16.1 (was: SSSD 1.16.0)

On one hand I would like to defer this ticket, on the other hand this seems like something that can be done in a couple of minutes, so why not knock the ticket away /if/ we know what to document.

I looked at the current enumeration documentation and I think we already discourage the user from enabling it. What I miss in the text is, silly as it sounds, what actually does it mean to enumerate the domain. I've seen in RH support cases that often admins are confused that without enumeration, secondary groups won't show up.

So, tl;dr, I would prefer to explicitly say what enumeration is and say that saving large amount of data might block the sssd_be process which might even become unresponsive and be killed.

Let's discuss in a PR, not in the bug tracker..

https://github.com/SSSD/sssd/pull/482

Metadata Update from @jhrozek:
- Issue assigned to jhrozek

Metadata Update from @jhrozek:
- Issue tagged with: PR, postpone-to-2-0

@jhrozek
Why is this ticket labeled as posponed-2.0 but milestone is 1.16.1?

See sssd-devel, the tags are just a proposal. I'm waiting for a feedback from other developers, if there is none, I will just triage the tickets as I proposed, but I don't want to do that before giving others time to react.

master:

  • c6a4ef46fa81f40b48000e334090982a9f4813e0

sssd-1-14:

  • a18da259efe44270a83f28829ecd6f4dfce4018a

sssd-1-13:

  • 44553b0989bd3dc7521c61a7e505096b18e3aab4

Metadata Update from @lslebodn:
- Issue untagged with: postpone-to-2-0
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

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

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.
Metadata

PR docs

None
None
High
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.