Bug 259819

Summary:	certain nfs mount options not supported
Product:	[openSUSE] openSUSE 11.0	Reporter:	Elmar Stellnberger <estellnb>
Component:	YaST2	Assignee:	Martin Vidner <mvidner>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Minor
Priority:	P3 - Medium	CC:	mvidner, ro
Version:	Alpha 2
Target Milestone:	---
Hardware:	i686
OS:	SuSE Linux 10.1
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Elmar Stellnberger 2007-04-02 10:59:04 UTC

nfs-mount: link_relative not supported any more
nfs-export: nohide-option has no effect (documentation says it is available!)
If configured via YaST2 user is not informed about any error messages at server reload!

Comment 1 Thomas Fehr 2007-04-04 08:19:38 UTC

yast2-storage does not have anything to do with nfs mounts.
I assume this is related to yast2-nfs-client

Comment 2 Martin Vidner 2007-04-04 12:49:47 UTC

> nfs-mount: link_relative not supported any more

That option is only available in the userspace server (nfs-server.rpm), not in the kernel one (nfs-utils.rpm).

> nfs-export: nohide-option has no effect (documentation says it is available!)

Are you not making this mistake?
man exports:
  The nohide option is currently only effective on single host exports.  It does not work reliably with netgroup, subnet,  or  wildcard exports.

> If configured via YaST2 user is not informed about any error messages at server
> reload!
>

Comment 3 Andreas Jaeger 2007-08-11 13:33:54 UTC

Martin, what information do you need?

Comment 4 Martin Vidner 2007-09-13 08:49:25 UTC

yast2-nfs-server gets the options as a string and does almost no checks on them. That makes it very easy to use invalid option combinations, which I believe was the case here and that was what I was trying to verify with Elmar.

The part about hiding error messages is a valid bug.
I think that we should extend the Service module to provide Service::Errors() if Service::Start/Stop/Restart...() has failed.

Originally reported on 10.2, moving to 11.0 because we only fix red bugs for 10.3 now.

Comment 5 Martin Vidner 2008-04-04 15:28:45 UTC

Changing maintainers.

Comment 6 Lukas Ocilka 2008-05-20 22:10:57 UTC

Closing as LATER for ENOTIME, Sorry.
Some of them might be closed as NOTAPPLICABLEANYMORE (which needs further checking).

Comment 7 Stephan Kulow 2008-06-25 09:10:38 UTC

mass reopening of later+remind bugs of 11.0

Comment 8 Katarina Machalkova 2008-08-07 08:36:20 UTC

Hm, why this one ended up assigned to me? This seems to be nfs-server (not client) issue

Comment 9 Martin Vidner 2010-11-02 14:52:22 UTC

This bug has been open for long but I haven't found the to fix it,
so now I close it. Sorry.

If you still care about it, please reopen it.