RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 692221 - Test lock failover when making NFSv4 servers active/passive HA
Summary: Test lock failover when making NFSv4 servers active/passive HA
Keywords:
Status: CLOSED DUPLICATE of bug 595547
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: resource-agents
Version: 6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Lon Hohberger
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-30 17:59 UTC by Perry Myers
Modified: 2011-03-30 20:36 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 692220
Environment:
Last Closed: 2011-03-30 20:35:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Perry Myers 2011-03-30 17:59:32 UTC 
The RHEL 5 bug this is cloned from references NFSv3 servers since that is default in RHEL5.  In RHEL 6 NFSv4 should be used, but we'll need to provide different config information than what is provided below.

+++ This bug was initially created as a clone of Bug #692220 +++

Description of problem:
rgmanager supports making NFSv3 servers highly available in an active/passive manner when backed by a non-clustered filesystem.  In this configuration scenario, you would want to be able to fail over the locks from one server to another so that the passive node can immediately pick up where the failed server left off.

This lock failover has not been extensively tested in a while, so this bug is to track testing of lock failover specifically.

Notes:

> 1) Add this to /etc/sysconfig/nfs:
> 
>    STATDARG="-H /usr/sbin/clunfslock"
> 
> 2) In cluster.conf, your service _MUST_ be structured like this; if you
> don't get the dependency chains just right, it will not work:
> 
>    ...
>    <resources>
>      <nfsexport name="nfsexports"/>
>    </resources>
>    ...
>    <service name="foo" nfslock="1" ... >
>      <fs name="fs1" ... >
>        <nfsexport ref="nfsexports">
>          <nfsclient ... />
>          <nfsclient ... />
>          ...
>        </nfsexport>
>      </fs>
>      <fs name="fs2" ... >
>        <nfsexport ref="nfsexports">
>          <nfsclient ... />
>          <nfsclient ... />
>          ...
>        </nfsexport>
>      </fs>
>      <ip ... />
>    </service>
Comment 2 Lon Hohberger 2011-03-30 20:03:12 UTC 
Lock failover should work with v4 today.

There is a difference, however: only one v4 server is allowed per cluster.  This is a limitation with how v4 recovery is done in the Linux implementation.

    <service name="foo" ... >
      <fs name="fs1" ... >
        <nfsserver name="nfsserver">
          <nfsclient ... />
          <nfsclient ... />
          ...
        </nfsserver>
      </fs>
      <ip ... />
    </service>
Comment 4 Lon Hohberger 2011-03-30 20:18:03 UTC 
Actually, the same agent on RHEL6 should work with v3 recovery too, according to the original bugzilla:

https://bugzilla.redhat.com/show_bug.cgi?id=595547#c27
Comment 6 Lon Hohberger 2011-03-30 20:35:58 UTC 

*** This bug has been marked as a duplicate of bug 595547 ***
Comment 7 Lon Hohberger 2011-03-30 20:36:32 UTC 
V4 lock failover is not something that needs to be explicitly configured on RHEL6.  It's part of the "nfsserver" resource agent.
Note You need to log in before you can comment on or make changes to this bug.