Bug 748275
Summary: | For some configurations, idmapd needs to access DNS | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Göran Uddeborg <goeran> |
Component: | nfs-utils | Assignee: | Steve Dickson <steved> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | amessina, bfields, jlayton, steved |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | nfs-utils-1.2.5-3.fc16 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-11-19 06:04:03 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Göran Uddeborg
2011-10-23 20:41:25 UTC
I seem to be having a similar problem using a freshly installed Fedora 16 VM for testing, except that even when I specify the Domain in /etc/idmapd.conf and restart the nfs-idmap.service, nothing changes and I continue to get: Nov 12 11:48:40 f16 rpc.idmapd[1619]: libnfsidmap: Unable to determine the NFSv4 domain; Using 'localdomain' as the NFSv4 domain which means UIDs will be mapped to the 'Nobody-User' user defined in /etc/idmapd.conf Nov 12 11:48:40 f16 rpc.idmapd[1619]: libnfsidmap: using (default) domain: localdomain Nov 12 11:48:40 f16 rpc.idmapd[1619]: libnfsidmap: Realms list: 'LOCALDOMAIN' Nov 12 11:48:40 f16 rpc.idmapd[1619]: libnfsidmap: loaded plugin /lib/libnfsidmap/nsswitch.so for method nsswitch Nov 12 11:48:40 f16 rpc.idmapd[1619]: Expiration time is 600 seconds. Nov 12 11:48:40 f16 rpc.idmapd[1619]: nfsdopenone: Opening /proc/net/rpc/nfs4.nametoid/channel failed: errno 2 (No such file or directory) In /etc/idmapd.conf, I have specified [General] Verbosity = 5 Domain = messinet.com [Mapping] Nobody-User = nfsnobody Nobody-Group = nfsnobody No matter what I try, i am not able to get ID mapping working. Perhaps worth noting is that I'm using the nfs-secure.service (In reply to comment #1) > I seem to be having a similar problem using a freshly installed Fedora 16 VM > for testing, except that even when I specify the Domain in /etc/idmapd.conf and [...] > > No matter what I try, i am not able to get ID mapping working. Perhaps worth > noting is that I'm using the nfs-secure.service So added an After=network.target to the [Unit] section of /lib/systemd/system/nfs-idmap.service did not help? *** Bug 751339 has been marked as a duplicate of this bug. *** Unfortunately, it does not. It's as if it's completely ignoring the 'Domain = messinet.com' parameter. Though I know the file is getting read, as I can change the Nobody-User or Nobody-Group and see those changes take effect. The following are from the virtual machine, in case these are related. ~]# cat /etc/resolv.conf # Generated by NetworkManager domain messinet.com search messinet.com virt.messinet.com nameserver 192.168.1.3 nameserver 192.168.2.5 ~]# cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 Anthony, I don't think you hare hit by this bug, but by bug 746497. Try to comment out ALL settings from idmapd.conf except for Domain. (Add a number of "-v" to RPCIDMAPDARGS in /etc/sysconfig/nfs to make it verbose that way instead.) Retry and see if it behaves differently. nfs-utils-1.2.5-3.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/nfs-utils-1.2.5-3.fc16 Package nfs-utils-1.2.5-3.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing nfs-utils-1.2.5-3.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-15921 then log in and leave karma (feedback). This change fixes it for clients, and I've given karma. There is nothing that makes nfs-idmap to wait for named to come up on the DNS server, so that case I still have to handle with a local configuration. But maybe that is the intention? The combination is obviously much less common. Since filing this bugzilla, I've learnt one can add a file to /etc/systemd/system which includes the one from /lib/systemd/system. So doing a local configuration to add "after named" isn't as tricky as I first thought. On the other hand, adding "after named" too to the standard nfs-idmap.service wouldn't hurt the common case. On a system which doesn't run named, the "after named" declaration will have no effect. Unless I've misunderstood things. (In reply to comment #8) > This change fixes it for clients, and I've given karma. > > There is nothing that makes nfs-idmap to wait for named to come up on the DNS > server, so that case I still have to handle with a local configuration. But > maybe that is the intention? The combination is obviously much less common. > > Since filing this bugzilla, I've learnt one can add a file to > /etc/systemd/system which includes the one from /lib/systemd/system. So doing > a local configuration to add "after named" isn't as tricky as I first thought. > > On the other hand, adding "after named" too to the standard nfs-idmap.service > wouldn't hurt the common case. On a system which doesn't run named, the "after > named" declaration will have no effect. Unless I've misunderstood things. I agree with this... I throw it in on an upcoming commit... nfs-utils-1.2.5-3.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |