Bug 808863 – nfs-server.service should start after named.service (systemd)

Bug 808863 - nfs-server.service should start after named.service (systemd)

Summary:	nfs-server.service should start after named.service (systemd)

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	nfs-utils (Show other bugs)
Sub Component:
Version:	16
Hardware:	x86_64 Linux

Priority	unspecified Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Steve Dickson
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2012-04-01 06:57 EDT by Rolf Fokkens
Modified:	2012-11-08 11:11 EST (History)
CC List:	3 users (show)

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

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: 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):
nfs-utils-1.2.5-5.fc16.x86_64

How reproducible:
50%?

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:
http://lists.fedoraproject.org/pipermail/scm-commits/2011-October/666919.html
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.