Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Following an update to RHEL7.5, AD users home directory is set to '/'.
For example:
getent passwd <user>@<AD domain>
<user>@<AD domain>:*:988808870:988808870:<user name>:/:/bin/bash
Rebooting the IdM server fixes the issue, but it comes back after a while.
This issue is related to the magic private group (mpg) code which makes sure that with algorithmic id-mapping users from AD (sub-domain users) are automatically assigned a user private group. Since the private groups does not exists as a real group a lookup for this group uses a fallback to a user lookup.
If now the user private group is looked up while the cached user entry is exprired the backend first tries to find a matching group fails and falls back to a user lookup. Now two issues happen. First the user is looked up in the Global Catalog which will remove attribute from the cache which are not replicated to the Global Catalog, e.g. the shell or a home directory defined in AD. Second the code which adds the home directory attribute to the cache user object was not able to find the user object because the original request was a group lookup and the used call to search the cache was not aware of MPGs.
Reproducer:
[root@f26-ipa ~]# systemctl stop sssd.service ; rm -f /var/log/sssd/* ; rm -f /var/lib/sss/db/* ; systemctl start sssd.service
[root@f26-ipa ~]# getent passwd tu1
tu1:*:1367201104:1367201104:t u:/home/ad.devel/tu1:/bin/sh
[root@f26-ipa ~]# sss_cache -E
[root@f26-ipa ~]# getent group 1367201104
tu1:*:1367201104:
[root@f26-ipa ~]# getent passwd tu1
tu1:*:1367201104:1367201104:t u:/:
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.
https://access.redhat.com/errata/RHSA-2018:3158