Bug 212313 - nfs mounts in kickstart %post fail - portmap not running
Summary: nfs mounts in kickstart %post fail - portmap not running
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-10-26 06:51 UTC by Steve Cliffe
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-10-30 19:16:31 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

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)


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