Bug 1400546
Summary: | After ganesha node reboot/shutdown, portblock process goes to FAILED state | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Soumya Koduri <skoduri> |
Component: | common-ha | Assignee: | bugs <bugs> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.9 | CC: | aloganat, amukherj, bugs, jthottan, kkeithle, oalbrigt, rhs-bugs, skoduri, storage-qa-internal |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.9.1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1399154 | Environment: | |
Last Closed: | 2017-03-08 10:20:15 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1399154 | ||
Bug Blocks: | 1398261 |
Description
Soumya Koduri
2016-12-01 13:20:22 UTC
REVIEW: http://review.gluster.org/15994 (common-HA: Increase timeout for portblock RA of action=unblock) posted (#1) for review on release-3.9 by soumya k (skoduri) COMMIT: http://review.gluster.org/15994 committed in release-3.9 by Kaleb KEITHLEY (kkeithle) ------ commit b60607e88d27295bb61e0365e2b23bf54af109f3 Author: Soumya Koduri <skoduri> Date: Mon Nov 28 17:56:35 2016 +0530 common-HA: Increase timeout for portblock RA of action=unblock Portblock RA of action type unblock stores the information about the client/server IPs connection in tickle_dir folder created in the shared storage. In case of node shutdown/reboot there could be cases wherein shared_storage may become unavailable for sometime. Hence increase the timeout to avoid that resource agent going into FAILED state. This is backport of below mainline patch - - http://review.gluster.org/15947 >Change-Id: I4f98f819895cb164c3a82ba8084c7c11610f35ff >BUG: 1399154 >Signed-off-by: Soumya Koduri <skoduri> >Reviewed-on: http://review.gluster.org/15947 >Smoke: Gluster Build System <jenkins.org> >CentOS-regression: Gluster Build System <jenkins.org> >Reviewed-by: Kaleb KEITHLEY <kkeithle> >Reviewed-by: Niels de Vos <ndevos> >NetBSD-regression: NetBSD Build System <jenkins.org> >Reviewed-by: jiffin tony Thottan <jthottan> >(cherry picked from commit 1b2b5be970f78cc32069516fa347d9943dc17d3e) Change-Id: I8e590a1b21c2a73d324e0a20c17378c593c5ebd5 BUG: 1400546 Signed-off-by: Soumya Koduri <skoduri> Reviewed-on: http://review.gluster.org/15994 Reviewed-by: jiffin tony Thottan <jthottan> Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Kaleb KEITHLEY <kkeithle> This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.9.1, please open a new bug report. glusterfs-3.9.1 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/gluster-users/2017-January/029725.html [2] https://www.gluster.org/pipermail/gluster-users/ |