sssd does not handle groups renaming correctly

Bug #1383682 reported by boris
270
This bug affects 4 people
Affects Status Importance Assigned to Milestone
sssd (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.5 LTS
Release: 12.04
Codename: precise

$ dpkg -l sssd
ii sssd 1.8.6-0ubuntu0.3 System Security Services Daemon

Description of problem:
We changed one of the groups name in MSAD that was defined as Unix group from
uppercase to lowercase. After that we noticed problems with some of the
services. In sssd_nss.log we got error messages:

(Fri Oct 14 10:03:31 2011) [sssd[nss]] [nss_cmd_getgrgid_search] (0): getgrgid
call returned more than one result !?!

Problems:

1. Checking groups in domain resulted in this:
[root@SERVERNAME db]# getent group |grep -i gr
GROUPGROUP:*:10069:username
groupgroup:*:10069:username

2. Cache was not updated correctly even after we removed group from Domain and
added it again.
[root@SERVERNAME db]# getent group |grep -i gr
GROUPGROUP:*:10069:username
groupgroup:*:10113:username

We got expected result only after removing cache from /var/lib/sss/db
directory. Resetting service didn't help.
[root@SERVERNAME db]# getent group |grep -i gr
groupgroup:*:10113:username

This was fixed by developers of sssd and fix was merged to upstream:
https://git.fedorahosted.org/cgit/sssd.git/commit/?id=42fb63b478058d3eb9a483e640958bd63114d309

Would you, please, merge this fix to ubuntu's sssd precise version? Thanks.

Tags: precise
boris (bb-kernelpanic)
information type: Public → Public Security
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in sssd (Ubuntu):
status: New → Confirmed
Revision history for this message
Denis (dekutin) wrote :

This bug affects sssd=1.8.6-0ubuntu0.3 from precise-updates, but do not sssd=1.8.2-0ubuntu1 from precise repositories.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

That commit has been upstream since 1.5.16..

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

but it actually got reverted between 1.8.2..1.8.6:

commit 4f2d70c17a68868b1295f2d6d7bf9e4acea3ae19
Author: Jakub Hrozek <email address hidden>
Date: Fri May 11 16:27:46 2012 +0200

    SYSDB: Handle user and group renames better

tags: added: precise
tags: added: upgrade-software-version
Revision history for this message
Sebastien Bacher (seb128) wrote :

is that still an issue in newer versions?

tags: removed: upgrade-software-version
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.