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. Version-Release number of selected component (if applicable): ------------------------------------------------------------- [root@gqas013 tmp]# rpm -qa|grep ganesha glusterfs-ganesha-3.8.4-26.el7rhgs.x86_64 nfs-ganesha-gluster-2.4.4-6.el7rhgs.x86_64 nfs-ganesha-debuginfo-2.4.4-6.el7rhgs.x86_64 nfs-ganesha-2.4.4-6.el7rhgs.x86_64 [root@gqas013 tmp]# [root@gqas013 tmp]# [root@gqas013 tmp]# rpm -qa|grep libnti libntirpc-1.4.3-1.el7rhgs.x86_64 libntirpc-devel-1.4.3-1.el7rhgs.x86_64 [root@gqas013 tmp]# [root@gqas013 tmp]# rpm -qa|grep pacem pacemaker-cluster-libs-1.1.16-10.el7.x86_64 pacemaker-cli-1.1.16-10.el7.x86_64 pacemaker-1.1.16-10.el7.x86_64 pacemaker-libs-1.1.16-10.el7.x86_64 [root@gqas013 tmp]# [root@gqas013 tmp]# rpm -qa|grep coros corosynclib-2.4.0-9.el7.x86_64 corosync-2.4.0-9.el7.x86_64 [root@gqas013 tmp]# [root@gqas013 tmp]# rpm -qa|grep resource-ag resource-agents-3.9.5-100.el7.x86_64 [root@gqas013 tmp]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.4 Beta (Maipo) [root@gqas013 tmp]# How reproducible: ----------------- Easily,every time. Steps to Reproduce: ------------------- 1. Run IO continuously and kill Ganesha 2. Observe IO on mount Actual results: --------------- IO continues inspite of the grace period. Expected results: ----------------- Writes should be stopped for 90 secs when grace is entered.
qa_acking as discussed in triage meet
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.
upstream patch : https://review.gluster.org/17534
I confirmed with the pcs developers that this was a behavioral change from 7.3 to 7.4, as the fix for Bug 1395226. The changed command in Comment 10 has the correct syntax, which will work on both 7.3 and 7.4.
downstream patch : https://code.engineering.redhat.com/gerrit/#/c/108924/
Verified on nfs-ganesha-2.4.4-10.el7rhgs.x86_64,glusterfs-ganesha-3.8.4-31.el7rhgs.x86_64
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2774