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.
Bug 1432313 - NFSv4 client mount shows uid=4294967294 when remounted after 600 seconds
Summary: NFSv4 client mount shows uid=4294967294 when remounted after 600 seconds
Keywords:
Status: CLOSED DUPLICATE of bug 1408330
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nfs-utils
Version: 7.3
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: ChunYu Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-15 05:13 UTC by Taketo Kabe
Modified: 2017-05-25 13:21 UTC (History)
7 users (show)

Fixed In Version: kernel-3.10.0-616.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-15 06:25:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
CentOS 12950 0 None None None 2017-03-15 05:13:40 UTC

Description Taketo Kabe 2017-03-15 05:13:41 UTC 
Description of problem:
When id-mapping feature of NFSv4 is enabled, and NFS client mounts it,
on first mount the id-mapping works as expected
(uid# of a file is shown mapped in respect of client machine)

but after 600 seconds and umount - mount ing,
all of uid# and gid# shows up as 4294967294 ((uid_t)(-2)).

After 300 seconds, and umount - mount ing,
id-mapping comes back. Back to beginning.


Version-Release number of selected component (if applicable):
kernel-3.10.0-514.10.2.el7.x86_64
nfs-utils-1.3.0-0.33.el7.x86_64

How reproducible: always


Steps to Reproduce:
Both NFS server and client is RHEL 7.3.

* On NFS server: Prepare NFS /etc/exports:
  /export/foo  172.16.xx.xx/24(rw,no_root_squash,sec=sys)
* NFS server: prepare a random file:
  # echo abc > /export/foo/bar
  # chown 2:2 /export/foo/bar
* NFS Server: enable id-mapping
  # echo N > /sys/module/nfsd/parameters/nfs4_disable_idmapping
* NFS Server: start nfs service
  # systemctl start nfs

NFS client should NOT have nfs server running.

* On NFS Client: mount the share by NFSv4.
  # mount -o nfsvers=4 172.16.yy.yy:/export/foo /mnt
* Verify that user and group name is properly mapped. (expected)
  # ls -l /mnt
* NFS Client: wait for 600 seconds, until
  # grep id_ /proc/keys
  shows "id_resolver" keys as "expd" (expired).
* NFS Client: remount the share.
  # umount /mnt
  # mount -o nfsvers=4 172.yy.yy.yy:/export/foo /mnt
* NFS Client:
  # ls -l /mnt

Actual results:
# ls -l /mnt
 -rw-r--r--. 1 4294967294 4294967294 4 3? 14 16:34 bar


Expected results:
# ls -l /mnt
 -rw-r--r--. 1 daemon daemon 4 3? 14 16:34 bar


Additional info:
This symptom surfaced since fix of
  nfsidmap not setting key timeouts 
  https://bugzilla.redhat.com/show_bug.cgi?id=1161222

This symptom will be fixed by kernel.org upstream commit:
https://patchwork.kernel.org/patch/5336901/
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=0b0a84154eff56913e91df29de5c3a03a0029e38
Comment 2 ChunYu Wang 2017-03-15 06:25:27 UTC 
(In reply to Taketo Kabe from comment #0)
> Description of problem:
> When id-mapping feature of NFSv4 is enabled, and NFS client mounts it,
> on first mount the id-mapping works as expected
> (uid# of a file is shown mapped in respect of client machine)
> 
> but after 600 seconds and umount - mount ing,
> all of uid# and gid# shows up as 4294967294 ((uid_t)(-2)).


Hi, Kabe,

Thanks for your detailed reports, your reproducers are handy and accurate. We have already noticed this problem and filed it as another one:

Bug 1408330 - nfs-utils-1.3.0-0.33 causes key expiration problem and intermittent uid/gid 4294967294

> Steps to Reproduce:
> 1. nfsv4 server and nfsv4 client, both running RHEL 7.3
> 2. wait 10 minutes for key to expire from keyring (as shown by nfsidmap -l)
> 3. ls -l shows uid/gid intermittently 4294967294 instead of correct value for > 5 minutes
> 4. at the end of this 5 minutes, the key reappears in the keyring and things > > return to normal
> 5. Go to step #2

As that bug is private, I will try to clone some fixing status here and notice you if necessary.

Thanks,
ChunYu Wang

*** This bug has been marked as a duplicate of bug 1408330 ***
Comment 3 Anze Zagar 2017-05-25 13:21:59 UTC 
When will this kernel-3.10.0-616.el7 be released in form of errata update?
Note You need to log in before you can comment on or make changes to this bug.