Bug 727338

Summary: autofs appears to mount with IP, changing df output
Product: Red Hat Enterprise Linux 5 Reporter: Kendrick Gay <kgay>
Component: autofsAssignee: Ian Kent <ikent>
Status: CLOSED DUPLICATE QA Contact: yanfu,wang <yanwang>
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.7CC: ikent, wburrows
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-02 02:49:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Kendrick Gay 2011-08-01 20:53:14 UTC 
Description of problem:
After going from autofs-5.0.1-0.rc2.143.el5_6.2 (RHEL5u6) to autofs-5.0.1-0.rc2.156.el5 (RHEL5u7), df shows the IP for NFS shares mounted by autofs:

# df
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda3              15G  4.5G  9.3G  33% /
/dev/sda6              92G   33M   88G   1% /scratch
/dev/sda5             9.7G  478M  8.7G   6% /var
/dev/sda1              99M   23M   72M  24% /boot
tmpfs                 7.9G     0  7.9G   0% /dev/shm
192.168.1.249:/opt    284G   81G  189G  30% /opt
192.168.1.249:/admin  548G   30G  490G   6% /admin

Appears df reports whatever's sent to it by the mount command, which appears to suggest autofs is mounting with the IP instead of the FQDN.

This does not exist in RHEL6u1 release of autofs.

Version-Release number of selected component (if applicable):
autofs-5.0.1-0.rc2.156.el5

How reproducible:
Everytime.

Steps to Reproduce:
1. Setup mount with autofs
2. Start autofs
3. Run 'df'
  
Actual results:
df reports <ip>:<path> as if autofs has mounted with the IP instead of the FQDN

Expected results:
df should report <fqdn>:<path>

Additional info:
Comment 1 Ian Kent 2011-08-02 02:49:06 UTC 
This is a known problem and it will be fixed in the next
release. I'm marking this as a duplicate of the bug we
have for it.

You have marked this as severity high, so presumably
this is a serious problem for you. Have a look at the
discussion in bug 725536 and post a request to that
bug if you require a test package that includes the
change.

*** This bug has been marked as a duplicate of bug 725536 ***