[Bugs] [Bug 1461019] [Ganesha] : Grace period is not being adhered to on RHEL 7.4 ; Clients continue running IO even during grace.

bugzilla at redhat.com bugzilla at redhat.com
Wed Jun 14 11:46:38 UTC 2017


https://bugzilla.redhat.com/show_bug.cgi?id=1461019



--- Comment #3 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17534 committed in release-3.10 by Kaleb
KEITHLEY (kkeithle at redhat.com) 
------
commit ee1a7560f8c27cc2721347dae37729aba9bac2d6
Author: Kaleb S. KEITHLEY <kkeithle at redhat.com>
Date:   Tue Jun 13 07:36:50 2017 -0400

    common-ha: surviving ganesha.nfsd not put in grace on fail-over

    Behavior change is seen in new HA in RHEL 7.4 Beta. Up to now clone
    RAs have been created with "pcs resource create ... meta notify=true".
    Their notify method is invoked with pre-start or post-stop when one of
    the clone RAs is started or stopped.

    In 7.4 Beta the notify method we observe that the notify method is not
    invoked when one of the clones is stopped (or started).

    Ken Gaillot, one of the pacemaker devs, wrote:
      With the above command, pcs puts the notify=true meta-attribute
      on the primitive instead of the clone. Looking at the pcs help,
      that seems expected (--clone notify=true would put it on the clone,
      meta notify=true puts it on the primitive). If you drop the "meta"
      above, I think it will work again.

    And indeed his suggested fix does work on both RHEL 7.4 Beta and RHEL
    7.3 and presumably Fedora.

    Change-Id: Idbb539f1366df6d39f77431c357dff4e53a2df6d
    BUG: 1461019
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle at redhat.com>
    Reviewed-on: https://review.gluster.org/17534
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: soumya k <skoduri at redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=8kkgV5ZlYU&a=cc_unsubscribe


More information about the Bugs mailing list