Bug 808863 - nfs-server.service should start after named.service (systemd)
nfs-server.service should start after named.service (systemd)
Product: Fedora
Classification: Fedora
Component: nfs-utils (Show other bugs)
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Steve Dickson
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-04-01 06:57 EDT by Rolf Fokkens
Modified: 2012-11-08 11:11 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-11-08 11:11:45 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rolf Fokkens 2012-04-01 06:57:12 EDT
Description of problem: Sometimes during boot nfsd fails to do DNS lookups of hosts specified in /etc/exports/. This results in failing client connections.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. reboot your NFS/DNS server
2. Access NFS directories from one of your NFS clients
3. Notice access problems
Actual results:
STALE NFS handles, write access failure (depending on exports contents)

Expected results:
NFS access as before.

Additional info:
This will probably be solved in the 1.2.6 RPM:
But why wait?
Comment 1 Steve Dickson 2012-05-15 15:01:48 EDT
That patch was backported.... 

    After=network.target named.service rpcbind.service proc-fs-nfsd.mount var-lib-nfs-rpc_pipefs.mount

Try added the  named.service to the Requires= line to see if that helps

Note You need to log in before you can comment on or make changes to this bug.