#2952 Adding a nested group hierarchy breaks ghost/memberUid propagation
Closed: wontfix 4 years ago by pbrezina. Opened 8 years ago by jhrozek.

Given a group and its member:

dn: name=bottomgroup@LOCAL,cn=groups,cn=LOCAL,cn=sysdb
createTimestamp: 1454930267
gidNumber: 28512
name: bottomgroup@LOCAL
objectClass: group
ghost: testghost28512
isPosix: TRUE
lastUpdate: 1454930267
dataExpireTimestamp: 1454930266
member: name=inherit28511@LOCAL,cn=users,cn=LOCAL,cn=sysdb
memberuid: inherit28511@LOCAL
distinguishedName: name=bottomgroup@LOCAL,cn=groups,cn=LOCAL,cn=sysdb

dn: name=inherit28511@LOCAL,cn=users,cn=LOCAL,cn=sysdb
createTimestamp: 1454930254
fullName: Test User 28511
gecos: Test User 28511
gidNumber: 28511
homeDirectory: /home/testuser28511
loginShell: /bin/bash
name: inherit28511@LOCAL
objectClass: user
uidNumber: 28511
lastUpdate: 1454930254
dataExpireTimestamp: 1454930253
memberof: name=bottomgroup@LOCAL,cn=groups,cn=LOCAL,cn=sysdb
distinguishedName: name=inherit28511@LOCAL,cn=users,cn=LOCAL,cn=sysdb

And two existing groups:

dn: name=topgroup@LOCAL,cn=groups,cn=LOCAL,cn=sysdb
createTimestamp: 1454930278
gidNumber: 28514
name: topgroup@LOCAL
objectClass: group
isPosix: TRUE
lastUpdate: 1454930278
dataExpireTimestamp: 1454930277
member: name=midgroup@LOCAL,cn=groups,cn=LOCAL,cn=sysdb
distinguishedName: name=topgroup@LOCAL,cn=groups,cn=LOCAL,cn=sysdb

dn: name=midgroup@LOCAL,cn=groups,cn=LOCAL,cn=sysdb
createTimestamp: 1454930271
gidNumber: 28513
name: midgroup@LOCAL
objectClass: group
isPosix: TRUE
lastUpdate: 1454930271
dataExpireTimestamp: 1454930270
memberof: name=topgroup@LOCAL,cn=groups,cn=LOCAL,cn=sysdb
distinguishedName: name=midgroup@LOCAL,cn=groups,cn=LOCAL,cn=sysdb

When bottomgroup is added to midgroup, I would have expected both midgroup and topgroup to have testghost28512 as a ghost user and inherit28511 as memberUid. However, I get:

dn: name=topgroup@LOCAL,cn=groups,cn=LOCAL,cn=sysdb
createTimestamp: 1454930278
gidNumber: 28514
name: topgroup@LOCAL
objectClass: group
isPosix: TRUE
lastUpdate: 1454930278
dataExpireTimestamp: 1454930277
member: name=midgroup@LOCAL,cn=groups,cn=LOCAL,cn=sysdb
ghost: testghost28512
ghost: inherit28511@LOCAL
distinguishedName: name=topgroup@LOCAL,cn=groups,cn=LOCAL,cn=sysdb

So far putting into 1.14 beta, this bug might make its way back to a sooner release if we indeed find out this is a bug that is affecting users.

milestone: NEEDS_TRIAGE => SSSD 1.14 beta

Fields changed

rhbz: => todo

So far nobody complained, so this shouldn't block the 1.14 release.

milestone: SSSD 1.14 beta => SSSD 1.15 beta

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

7 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

4 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)

4 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/3993

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.

Metadata