Bug 962248 - mount.nfs rpc.statd is not running but is required for remote locking
Summary: mount.nfs rpc.statd is not running but is required for remote locking
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: rpcbind
Version: 19
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-13 00:07 UTC by Robert Lightfoot
Modified: 2013-05-13 04:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-13 04:10:38 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Screenshot of x86_64 at failure point tty5 (14.86 KB, image/png)
2013-05-13 00:07 UTC, Robert Lightfoot 		no flags Details
View All

Description Robert Lightfoot 2013-05-13 00:07:53 UTC 
Created attachment 747025 [details]
Screenshot of x86_64 at failure point tty5

Description of problem:
When using "linux inst.repo=nfs:ip.addr.of.server:/path/to/repository/" install halts for can't mount due to rpc.statd error

Version-Release number of selected component (if applicable):
Fedora-19-Beta-TC4 both i386 and x86_64 versions

How reproducible:
100% 

Steps to Reproduce:
1. Boot DVD and press escape at menu
2. Enter Command "linux inst.repo=nfs:ip.addr.of.server:/path/to/repository/"
3. 
  
Actual results:
Install halts for rpc.statd error

Expected results:
Successful install

Additional info:
Graphical NFS Install works successfully in both arch
Comment 1 Robert Lightfoot 2013-05-13 00:09:42 UTC 
Proposing as Beta Blocker as criteria specifically states NFS mount must work.
Comment 2 Robert Lightfoot 2013-05-13 01:17:52 UTC 
Removing proposal as Beta Blocker, this issue exists when using VirtualBox on Windows 7, but not when using qemu-kvm on Centos 6.
Comment 3 Robert Lightfoot 2013-05-13 04:10:38 UTC 
Closing as this was a network interface definition issue and not fedora caused.
Note You need to log in before you can comment on or make changes to this bug.