Bug 465966

Summary: mount.nfs returns incorrect exit code for failed mount
Product: Red Hat Enterprise Linux 5 Reporter: Jeff Moyer <jmoyer>
Component: nfs-utilsAssignee: Steve Dickson <steved>
Status: CLOSED ERRATA QA Contact: Martin Jenner <mjenner>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.4CC: coughlan, dkovalsk, duck, jlayton, rwheeler, steved, syeghiay
Target Milestone: betaKeywords: Regression
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-20 21:01:09 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:
Attachments:
Description Flags
Proposed patch none

Description Jeff Moyer 2008-10-07 13:49:07 UTC
Description of problem:
If you try to mount an export that is not exported to the client, you get an error message of permission denied, but mount returns exit code 0, indicating success.  This breaks the automounter, which needs to know that the mount failed.


Version-Release number of selected component (if applicable):
1.0.9-37.el5

How reproducible:
100%

Steps to Reproduce:
See problem description.
I will also check to see if the autofs rhts tests will catch this.

Comment 1 Steve Dickson 2008-10-07 14:11:42 UTC
It seem the regression happen with the fix to
   https://bugzilla.redhat.com/show_bug.cgi?id=438418

Comment 2 Steve Dickson 2008-10-07 14:21:14 UTC
Created attachment 319642 [details]
Proposed patch

Comment 3 Steve Dickson 2008-10-07 14:48:07 UTC
Fixed in nfs-utils-1.0.9-38.el5

Comment 5 Jeff Moyer 2008-10-07 14:58:20 UTC
I tested the updated package and found that:
1) it returns exit code 32 for the permission denied case
2) it returns success when it successfully mounts
3) automount behaviour has returned to normal.

Cheers.

Comment 8 errata-xmlrpc 2009-01-20 21:01:09 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-0107.html