RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
IPA supports nested group. That means for one group, there are direct user members and in-direct members (member in nested groups).
However, in Web UI, if one group has no direct user member, the UI page will show no user member at all. As long as there is one direct user member, all direct members and indirecst member will show up. This listing feature is inconsistent. 

Version-Release number of selected component (if applicable): ipa-server-selinux-2.0.0-23.el6.i686


How reproducible:


Steps to Reproduce:
1. create nested group: grp2 is member of grp1
2. let user21 and user22 is direct member of grp2, and user11 and user12 is direct member of grp1
3. when check user list for grp1, we can see all 4 users: user11, user12, user21, user22 are listed
4. now delete user11 and user22 from grp1
5. go back to same user list page for grp1, there is no user listed at all.
  
Expected results:
I expect the user listing behave is consistent: if we decide to show indirect member, then regardless if there is direct member, we should always show indirect member. Vise versa. 

Additional info:

Please retest using a daily build

I am not seeing any issues with displaying direct and/or indirect members with the newest build, but I would like Yi to take a look as I am not exactly sure of the scenario he was testing.

Any update?

my bug report based on the 6.1 release. And I don't see the same issue on the daily build. This bug can be closed as verified

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Do not document

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.

http://rhn.redhat.com/errata/RHSA-2011-1533.html