[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]

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

Kaleb KEITHLEY <kkeithle at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |Triaged
             Status|NEW                         |ASSIGNED
           Assignee|bugs at gluster.org            |kkeithle at redhat.com



--- Comment #1 from Kaleb KEITHLEY <kkeithle at redhat.com> ---
Description of problem:
-----------------------

4 node cluster,4 clients accessing the export via v4.

Kill NFS-Ganesha on any node.

Grace period should be entered and any and all IO should halt for 90 seconds.

I observed that other clients continued running their IO,which is unusual.

This may be a regression introduced in latest pacemaker/corosync bits. 

============================================================================

Ken Gaillot writes in email
> clone RA is created with
>
>   pcs resource create nfs-grace ocf:heartbeat:ganesha_grace --clone meta
> notify=true

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.

If that exact command worked on 7.3, pcs behavior might have changed.
Double-check, and if so, I'll ask the pcs devs to look into it.

============================================================================

Indeed changing the resource create from

  `pcs resource create nfs-grace ocf:heartbeat:ganesha_grace --clone meta
 notify=true`

to

  `pcs resource create nfs-grace ocf:heartbeat:ganesha_grace --clone
notify=true`

restores the original behavior seen in RHEL 7.3 and earlier.

Please check with the pcs devs and we will confirm that the changed command
also works correctly on RHEL 7.3.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.