Bug 1033918 - autofs doesn't work for nfs?
Summary: autofs doesn't work for nfs?
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: autofs
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ian Kent
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-24 10:16 UTC by Jason Haar
Modified: 2015-06-30 00:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-30 00:45:04 UTC
Type: Bug


Attachments (Terms of Use)

Description Jason Haar 2013-11-24 10:16:33 UTC
Description of problem:

installed autofs, started it, but it cannot mount the nfsv3 share that worked fine under autofs in previous Fedora

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


How reproducible:

everytime

Steps to Reproduce:
1. install and start autofs
2. do a "ls -l /net/server" 
3. 

Actual results:

no listing of shares

Expected results:

listing of shares

Additional info:

"mount server.name:/share /dir" works just fine, but "ls -l /net/server.name" or "ls -l /net/server.name/share" does not. This worked on previous Fedora - doesn't work in FC20

I've tried editing /etc/sysconfig/autofs and setting MOUNT_NFS_DEFAULT_PROTOCOL=3, and even "LOGGIN=debug" didn't point at any issue.

syslog shows the following

automount[17461]: get_exports: lookup(hosts): exports lookup failed for server.name

automount[17461]: key "server.name" not found in map source(s).

That smells related - but doesn't help me. I certainly cannot remember having to do anything special to make this work before...

Comment 1 Ian Kent 2013-11-25 01:54:16 UTC
Try revision 35 from updates testing.

Comment 2 Ferry Huberts 2013-12-03 19:15:20 UTC
I have this too.
And there is no rev 35 on updates-testing...
(I installed F20 beta through fedup from F19)

Comment 3 Fedora End Of Life 2015-05-29 09:50:21 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-06-30 00:45:04 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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