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:
Please add doc text for this known issue.
Please review and signoff the edited doc text.
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.
Doc text looks fine
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/
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.
Sahina, Please review and sign-off the edited doc text.
Looks good
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