Bug 710263

Summary: rpc.statd doesn't work without valid RDNS for NFS server
Product: Red Hat Enterprise Linux 6 Reporter: Kelsey Cummings <kgc>
Component: nfs-utilsAssignee: Steve Dickson <steved>
Status: CLOSED CURRENTRELEASE QA Contact: yanfu,wang <yanwang>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0   
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-11 18:14:02 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 Kelsey Cummings 2011-06-02 20:56:09 UTC 
Description of problem:

rpc.statd doesn't work when a host does not have rdns when mounting by ip address.

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

nfs-utils-1.2.2-7

How reproducible:

Very.

Steps to Reproduce:
1. mount nfs server by ip address, eg, mount 172.16.255.14:/export /nfs/export
  
Actual results:

Locking does not work:

May 25 21:12:15 a rpc.statd[5850]: No canonical hostname found for 172.16.255.14
May 25 21:12:15 a rpc.statd[5850]: STAT_FAIL to a for SM_MON of 172.16.255.14
May 25 21:12:15 a kernel: lockd: cannot monitor 172.16.255.14

Expected results:

That locking would work.  Just like it is has in previous releases when just mounting by IP address where there are no reverse dns records.

Additional info:

It can easily be worked around by adding entries in /etc/hosts but this isn't expected behavior and could lead to confusion and issues including potential data corruption if the statd errors go unobservered when migrating from earlier releases.

This Debian bug report appears to be for the same issue.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579397