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.
DescriptionOndrej Valousek
2011-05-02 13:06:46 UTC
Description of problem:
I am booting a diskless RHEL-6 environment using dracut this way:
[victim@data ~]$ cat /proc/cmdline
initrd=rhel6-ws-boot/initramfs.img console=ttyS0,115200 console=tty0 root=nfs4:192.168.60.50:/vol/vol1/OS/rhel6/root crashkernel=256M@16M nomodeset vesa BOOT_IMAGE=rhel6-ws-boot/vmlinuz
The system boots up correctly with / mounted via nfs4 but all files are reported to be owned by root:nobody. I restarted rpc.idmapd with verbose output and it seems that there is no activity whatsoever performed by this daemon:
[root@data .snapshot]# rpc.idmapd -vvvf
rpc.idmapd: libnfsidmap: using domain: dublin.ad.s3group.com
rpc.idmapd: libnfsidmap: processing 'Method' list
rpc.idmapd: libnfsidmap: loaded plugin /usr/lib64/libnfsidmap/nsswitch.so for method nsswitch
rpc.idmapd: Expiration time is 600 seconds.
rpc.idmapd: nfsdopenone: Opening /proc/net/rpc/nfs4.nametoid/channel failed: errno 2 (No such file or directory)
rpc.idmapd: New client: 0
rpc.idmapd: New client: 2
..it stays so for ever (no matter if I try to mount something via nfs4, list content...
Note that this setup worked fine with RHEL-5
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info: