Bug 1106421

Summary: [Nagios] Server quorum status is pending when quorum is not enabled for any volume in the cluster
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Shruti Sampat <ssampat>
Component: nagios-server-addonsAssignee: Sahina Bose <sabose>
Status: CLOSED ERRATA QA Contact: Shruti Sampat <ssampat>
Severity: medium Docs Contact:
Priority: medium    
Version: rhgs-3.0CC: asriram, divya, dpati, knarra, rhsc-qe-bugs, rnachimu, sabose
Target Milestone: ---   
Target Release: RHGS 3.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: nagios-server-addons-0.2.1-1.el6rhs.noarch Doc Type: Bug Fix
Doc Text:
Previously, the Quorum status was a passive check. As a consequence, the Plugin status is displayed as Pending even if there is no issues with Quorum or quorum is not enabled. With this fix, a freshness check is added. If the plugin is not updated or results are stale by an hour, the freshness check is executed to update the plugin status. If there are no volumes with quorum enabled, the plugin status is displayed as UNKNOWN.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-29 05:26:06 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:    
Bug Blocks: 1087818, 1202842    

Description Shruti Sampat 2014-06-09 10:06:17 UTC
Description of problem:
------------------------

When none of the volumes have quorum enabled, the server quorum monitoring service for that cluster remains in the pending state after the auto-discovery command is run, and remains in that state with the status information as follows  -
"Service is not scheduled to be checked..."

Version-Release number of selected component (if applicable):
nagios-server-addons-0.1.1-2.el6rhs.x86_64
gluster-nagios-addons-0.1.1-1.el6rhs.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Setup a cluster of RHS nodes and create volumes.
2. Run auto-discovery to configure this cluster to be monitored by Nagios.

Actual results:
The server quorum monitoring service remains in pending state.

Expected results:
Server quorum service should be UNKNOWN and the Status Information should read "None of the volumes are enabled for server-side quorum"

Additional info:

Comment 1 Shalaka 2014-06-18 05:54:29 UTC
Please add doc text for this known issue.

Comment 2 Shalaka 2014-06-24 17:28:18 UTC
Please review and signoff the edited doc text.

Comment 3 Shruti Sampat 2014-08-21 12:31:38 UTC
A similar issue is that the state of the service remains as pending, when the volumes discovered by auto-discovery are already enabled with server quorum before being discovered. The service continues to remain in pending state until a passive check reporting gain or loss of quorum for any volume is received by the nagios server.

Comment 4 Sahina Bose 2014-09-17 05:25:41 UTC
Doc text looks fine

Comment 5 Sahina Bose 2014-11-12 06:25:24 UTC
NSCA plugins do not change status until a message is received from the hosts. In case of cluster quorum plugin, if no volumes have server side quorum turned on or if all nodes are up, then this plugin remains in Pending state.

Added a freshness check which executes every hour to check the status in case no state change has happened for an hour, to ensure that plugin status is updated regularly.

http://review.gluster.org/#/c/8023/
http://review.gluster.org/#/c/8016/

Comment 6 RamaKasturi 2015-06-18 07:27:09 UTC
Verified and works fine with build nagios-server-addons-0.2.1-2.el6rhs.noarch.

When there are no volumes with server quorum turned on after running configure-gluster-nagios the status of service will be changed to UNKNOWN with status information as "Server quorum not turned on for any volume" after an hour.

If user wants to see the change immediately, he can run an active check on the service to see the state change from pending to unknown.

Comment 7 Divya 2015-07-26 12:08:18 UTC
Sahina,

Please review and sign-off the edited doc text.

Comment 8 Sahina Bose 2015-07-27 04:59:00 UTC
Looks good

Comment 10 errata-xmlrpc 2015-07-29 05:26:06 UTC
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://rhn.redhat.com/errata/RHEA-2015-1494.html