Bug 246668

Summary: exportfs returns hostnames instead of IPs causing problems with nfsclient.sh
Product: [Retired] Red Hat Cluster Suite Reporter: Lon Hohberger <lhh>
Component: rgmanagerAssignee: Ryan O'Hara <rohara>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: low Docs Contact:
Priority: low    
Version: 4CC: cluster-maint, edamato, mgrac, tao
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-05-18 21:13:42 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
Fixes behavior
none
Fixes behavior none

Description Lon Hohberger 2007-07-03 19:18:01 UTC 
Description of problem:

Because exportfs tries DNS / host resolution of IPs when displaying the list of
exports (exportfs -v), exporting to a client via IP address in cluster.conf
causes an erroneous "nfsclient:<ip> missing" message.


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


How reproducible: 100%


Steps to Reproduce:
1. Create an nfsclient resource with an IP as the target
2. Attach the nfsclient resource to a service...
3. Start service
4. wait for status checks
  
Actual results: Resource is constantly restarted.

Expected results: Resource is not restarted since it wasn't a real error
Comment 1 Lon Hohberger 2007-07-03 19:18:01 UTC 
Created attachment 158469 [details]
Fixes behavior
Comment 2 Lon Hohberger 2007-07-03 19:19:14 UTC 
Created attachment 158470 [details]
Fixes behavior

This script can be dropped in /usr/share/cluster to fix the problem on live
systems.
Comment 3 Lon Hohberger 2007-09-24 20:18:33 UTC 
The real place to fix this is in exportfs - as in, providing a query to ask the
kernel if a particular export was still valid or not.
Comment 5 Lon Hohberger 2007-12-11 14:51:33 UTC 
How was this resolved ?  We never put it in a release...
Comment 8 Lon Hohberger 2008-01-28 19:54:18 UTC 
*** Bug 428702 has been marked as a duplicate of this bug. ***
Comment 10 Ryan O'Hara 2008-10-05 16:23:30 UTC 
Fixed in RHEL4 tree.
Comment 13 errata-xmlrpc 2009-05-18 21:13:42 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-1048.html