Red Hat Bugzilla – Bug 805921
Document the expectations about ghost users showing in the lookups
Last modified: 2013-02-21 04:21:58 EST
This bug is created as a clone of upstream ticket:
See ticket #1255 for the design of the new approach of dealing with fake/ghost users. There are some situations when fake/ghost users are removed from child groups but would still show up as a member of the parent group. It might look confusing and might cause some unnecessary bugs and tickets filed. To prevent this we need to clearly articulate how things would work with the new approach and what to expect.
where is this to be documented?
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Currently the expectations have only been documented in the upstream FAQ document - https://fedorahosted.org/sssd/wiki/FAQ
Would you prefer a better document such as the release notes? I don't think the man pages are a good place to include a low-level change like that.
As discussed with Kaushik, the proper place seems to be the release notes, so I've set the flag.
I cleaned up the FAQ, it was quite confusing. This is the link to the (hopefully correct now) upstream documentation: https://fedorahosted.org/sssd/wiki/FAQ#Idontseeanygroupmemberswhenrunninggetentgroupgroupname
Marking as MODIFIED because the upstream documentation has been corrected. I'll leave the FixedIn field blank.
Doc Text gives appropriate explanation and solution of the issue. Marking this bug verified.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.