#2982 SSSD complains about multiple groups having same GID
Closed: wontfix 2 years ago by pbrezina. Opened 6 years ago by ondrejv2.

I am getting the following error in syslog:
More groups have the same GID [10272] in directory server. SSSD will not work correctly.

I have only single group of that GID in AD. The problem occurs when I rename the group in AD.
It however does not seem to have any huge effect on SSSD functionality - seems much like annoying message only.

This happens because the renaming code and the member renaming code do not work at the moment (probably never did, looking at the history of the code..).

I'm touching this area for performance reasons in 1.14, so chances are we'll fix it there. An easy workaround is to purge the cache..

Let's put this one into 1.14 backlog and see if the LDAP provider changes make an effect. Not too urgent, though, since there is a workaround.

milestone: NEEDS_TRIAGE => SSSD 1.13.4

Fields changed

rhbz: => todo

Oops, wrong milestone,sorry.

milestone: SSSD 1.13.4 => SSSD 1.14 backlog

Since the 1.14 branch is transitioning into maintenance mode and new functionality is being developed in master which will become 1.15 eventually, I'm mass-moving tickets from the 1.14 backlog milestone to the "Future releases" milestone.

milestone: SSSD 1.14 backlog => SSSD Future releases (no date set yet)

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

5 years ago

Metadata Update from @thalman:
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch reset (from 0)
- Custom field review reset (from 0)
- Custom field sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue tagged with: Canditate to close

2 years ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

2 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/4023

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.