Red Hat Bugzilla – Bug 246668
exportfs returns hostnames instead of IPs causing problems with nfsclient.sh
Last modified: 2010-10-22 12:05:06 EDT
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
Created attachment 158469 [details]
Created attachment 158470 [details]
This script can be dropped in /usr/share/cluster to fix the problem on live
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.
How was this resolved ? We never put it in a release...
*** Bug 428702 has been marked as a duplicate of this bug. ***
Fixed in RHEL4 tree.
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.