Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 162824

Summary: Shared nfsclient references by multiple filesystems don't get monitored
Product: [Retired] Red Hat Cluster Suite Reporter: Eric Kerin <eric>
Component: rgmanagerAssignee: Lon Hohberger <lhh>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: cluster-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: RHBA-2005-738 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-10-07 16:52:14 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 Flags
Proposed fix none

Description Eric Kerin 2005-07-08 22:34:04 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.7.8-1.3.1

Description of problem:
Shared nfsclient resources do not get status monitor run against them if they are referenced multiple times.   This was originally posted by Birger Wathne on the linux-cluster mailing list.

In the config file below, only 5 of the 9 exports below get a status monitor, export1fs:h-nfs-root

The rest do not get checked since they are the second reference to the shared resource.

Relevant cluster.conf section---
    <fs fstype="ext3" name="export1fs" mountpoint="/exports/export1" device="/dev/LocalGroup01/Export1Vol00" options="acl"/>
    <fs fstype="ext3" name="export2fs" mountpoint="/exports/export2" device="/dev/LocalGroup01/Export2Vol00" options="acl"/>
    <fs fstype="ext3" name="export3fs" mountpoint="/exports/export3" device="/dev/LocalGroup01/Export3Vol00" options="acl"/>

    <nfsclient name="nis-hosts" target="" options="rw,sync"/>
    <nfsclient name="nis-hosts-ro" target="" options="ro,sync,no_root_squash"/>
    <nfsclient name="h-nfs-root" target="" options="rw,sync,no_root_squash"/>
    <nfsclient name="h-nfs-insecure" target="" options="rw,sync,insecure"/>
    <nfsclient name="h-nfs-insecure-ro" target="" options="ro,sync,no_root_squash,insecure"/>

  <service name="nfssvc">
    <fs ref="export1fs">
      <nfsexport name="export1fs">
        <nfsclient ref="h-nfs-root"/>
        <nfsclient ref="h-nfs-insecure-ro"/>
        <nfsclient ref="nis-hosts-ro"/>
    <fs ref="export2fs">
      <nfsexport name="export2fs">
        <nfsclient ref="h-nfs-root"/>
        <nfsclient ref="h-nfs-insecure"/>
        <nfsclient ref="nis-hosts"/>
    <fs ref="export3fs">
      <nfsexport name="export3fs">
        <nfsclient ref="h-nfs-root"/>
        <nfsclient ref="h-nfs-insecure"/>
        <nfsclient ref="nis-hosts"/>

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

How reproducible:

Steps to Reproduce:
1.Reference the same nfsclient shared resource in multiple filesystem nfsexport


Actual Results:  only 5 monitor commands are executed, instead of 9.

Expected Results:  All 9 exports are monitored.

Additional info:

Comment 1 Eric Kerin 2005-07-08 22:40:01 UTC
Created attachment 116552 [details]
Proposed fix

The proposed patch makes a copy of the resource action list in each resource
node that references a resource.  It then uses that list when checking the
status, so each use of the resource has it's own last checked timestamp for
each action.

Comment 3 Eric Kerin 2005-07-12 05:17:18 UTC
I received an email from Birger, stating that the patch did fix the nfs export
monitoring problem on his cluster.

Comment 4 Lon Hohberger 2005-07-12 14:58:39 UTC
Excellent.  Putting in STABLE, RHEL4, and HEAD.

Comment 5 Lon Hohberger 2005-07-12 15:27:39 UTC
I ran a regression test to ensure that there was no memory leaked; there wasn't.
 Patch is definitely acceptable.

Comment 6 Lon Hohberger 2005-07-12 15:35:07 UTC
Patches in.

Comment 8 Red Hat Bugzilla 2005-10-07 16:52:14 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 the 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.