Bug 212313

Summary:	nfs mounts in kickstart %post fail - portmap not running
Product:	[Fedora] Fedora	Reporter:	Steve Cliffe <scliffe>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-10-30 19:16:31 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 Steve Cliffe 2006-10-26 06:51:52 UTC

Description of problem:

Mounting of nfs filesystems in the %post section of kickstart fail due to
portmap not running. 

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

FC6 release

How reproducible:

Consistently reproducible

Steps to Reproduce:
1. mount.nfs nfsserver:/directory /mountpoint
2.
3.
  
Actual results:

Times out - unable to contact local portmap

Expected results:

Should mount filesystem

Additional info:

Using /usr/bin/mount instead of /sbin/mount.nfs works fine. 

Workaround is to start portmap in the %post section of the kickstart file before
attempting to mount nfs directories.

Comment 1 Jeremy Katz 2006-10-30 19:16:31 UTC

You need to use -o nolock if you're using mount from within the chroot.  A
portmapper _isn't_ running (and won't be)