Bug 751339

Summary: rpc.idmapd doesn't autoconfigure domain on startup
Product: [Fedora] Fedora Reporter: Jeff Layton <jlayton>
Component: nfs-utilsAssignee: Steve Dickson <steved>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: amessina, bfields, jlayton, sprabhu, steved
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-14 12:30:36 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Jeff Layton 2011-11-04 08:15:58 EDT
I recently switched my main workstation at home to f16. Since then, rpc.idmapd does not properly pick set the idmapping domain at boot time. If I go in after
booting and do a "service nfs-idmap restart" then it will work properly. It
also works properly if I set the domain explicitly in /etc/idmap.conf.

I suspect the problem is a boot-time ordering issue. rpc.idmapd is likely being started before the hostname is properly set on the machine. I'm not sure exactly how to fix this -- we may need some systemd expertise.

In any case -- perhaps it's time to move to the new idmapper anyway?
Comment 1 Steve Dickson 2011-11-14 12:30:36 EST

*** This bug has been marked as a duplicate of bug 748275 ***