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.
Description of problem:
Previous behavior of libnfsidmap was to do a name lookup of
nobody@DEFAULTDOMAIN (for both user and group), which does not match
the behavior of rpc.idmapd.
This patch makes libnfsidmap respect Nobody-User/Nobody-Group for
lookups, thus making the nfsidmap utility properly handle the case if
nobody@DEFAULTDOMAIN does not directly map to any user/group on the
system.
How reproducible:
100%
Steps to Reproduce:
1. Uncomment Nobody-User in /etc/idmapd.conf and set it to a value
2. Do a NFSv4 mount.
3. See what value is used when there is no valid id/gid mapping
Additional info:
commit f139de79d91e7773b5b98fe5aca5570f77c7aee9
Author: Christian Seiler <christian>
Date: Wed Aug 13 12:42:14 2014 -0400
libnfsidmap: respect Nobody-User/Nobody-Group
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://rhn.redhat.com/errata/RHBA-2015-0575.html
Description of problem: Previous behavior of libnfsidmap was to do a name lookup of nobody@DEFAULTDOMAIN (for both user and group), which does not match the behavior of rpc.idmapd. This patch makes libnfsidmap respect Nobody-User/Nobody-Group for lookups, thus making the nfsidmap utility properly handle the case if nobody@DEFAULTDOMAIN does not directly map to any user/group on the system. How reproducible: 100% Steps to Reproduce: 1. Uncomment Nobody-User in /etc/idmapd.conf and set it to a value 2. Do a NFSv4 mount. 3. See what value is used when there is no valid id/gid mapping Additional info: commit f139de79d91e7773b5b98fe5aca5570f77c7aee9 Author: Christian Seiler <christian> Date: Wed Aug 13 12:42:14 2014 -0400 libnfsidmap: respect Nobody-User/Nobody-Group