Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 1030135
Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.
Description of problem:
Customer is having a problem in that secondary groups will randomly disappear
and about 15 minutes later will reappear.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
secondary groups randomly disappear
secondary groups not disappear
Customer is using IPA server but is not using the default sssd.conf. It should
be mentioned again that about 15 minutes later his secondary groups will show
up when he runs the id command again.
design_review: => 0
milestone: NEEDS_TRIAGE => SSSD 1.11.3
review: True => 0
testsupdated: => 0
owner: somebody => lslebodn
Moving tickets that didn't make 1.11.3 to 1.11.4
milestone: SSSD 1.11.3 => SSSD 1.11.4
We're still talking to the customer who reported the issue. Currently it seems the problem was caused by a server misconfiguration, but we're still waiting on confirmation from the reporter. This ticket shouldn't block 1.11.4, so I'm moving it to 1.11.5 for the time being.
milestone: SSSD 1.11.4 => SSSD 1.11.5
We figured out what the bug was -- when both IPA (for id and auth) and LDAP backends (for sudo) are configured AND enumeration is selected, then the backend will run two concurrent enumeration tasks that might step on one another.
summary: sssd secondary groups will randomly disappear => If both IPA and LDAP are set up with enumeration on, two enum tasks are running
priority: major => critical
patch: 0 => 1
status: new => assigned
resolution: => fixed
status: assigned => closed
Metadata Update from @jhrozek:
- Issue assigned to lslebodn
- Issue set to the milestone: SSSD 1.11.5
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:
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.
to comment on this ticket.