Bug 1109702 - [Nagios] Cluster - quorum service displays information about a volume even after it is deleted
Summary: [Nagios] Cluster - quorum service displays information about a volume even af...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-nagios-addons
Version: rhgs-3.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: RHGS 3.0.3
Assignee: Sahina Bose
QA Contact: Shruti Sampat
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-16 07:40 UTC by Shruti Sampat
Modified: 2015-05-13 17:42 UTC (History)
9 users (show)

Fixed In Version: gluster-nagios-addons-0.1.13-1.el6rhs
Doc Type: Bug Fix
Doc Text:
Previously, even after a volume was deleted, the volume information continued to appear in the output of the Cluster-quorum service plugin. The plugin retains the information of the volume which lost the quorum and updates it only when the quorum is either lost or regained. With this fix, the stale information in the output is removed and the plugin output is displayed appropriately. Result: Information about deleted volumes is not present in plugin output
Clone Of:
Environment:
Last Closed: 2015-01-15 13:48:08 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0039 0 normal SHIPPED_LIVE Red Hat Storage Console 3.0 enhancement and bug fix update #3 2015-01-15 18:46:40 UTC

Description Shruti Sampat 2014-06-16 07:40:02 UTC 
Description of problem:
-------------------------

Consider a scenario where a volume is configured for with server-side quorum. When quorum is not met for that volume, the cluster - quorum service is critical. After it is regained, the service is OK with status information reading - 
"QUORUM: Server quorum regained for volume <vol-name>. Starting local bricks." . 

If the volume is deleted now, the cluster - quorum service will retain this status information until any further activity like quorum being lost or regained on another volume occurs.

This does not look right, because the volume no longer exists.

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

How reproducible:
Always

Steps to Reproduce:
1. Create a volume, configure server-side quorum on the volume.
2. Cause the volume to lose quorum, then regain it.
3. Stop the volume, and then delete it.

Actual results:
The cluster - quorum service retains status information about the deleted volume until further activity related to quorum on another volume occurs.

Expected results:
The cluster - quorum service should not show information related to non-existent volumes.

Additional info:
Comment 2 Sahina Bose 2014-11-12 06:20:01 UTC 
Each quorum lost message that nagios receives contains detail of individual volume and consolidating the volume names at nagios was not possible.

http://review.gluster.org/#/c/9095/ - posted patch to change the plugin message. Since quorum is lost for the entire cluster, message is now changed to not contain volume name.
Comment 3 Shalaka 2014-11-27 06:25:01 UTC 
Please add doc text for this bug.
Comment 4 Shruti Sampat 2014-11-27 12:04:20 UTC 
Verified as fixed in gluster-nagios-addons-0.1.13-1.el6rhs. 

Status information no longer mentions any volume. So is is seen as follows when quorum is lost and regained respectively -

QUORUM: Cluster server-side quorum lost.

QUORUM: Cluster server-side quorum regained.
Comment 5 Pavithra 2014-12-24 08:59:22 UTC 
Hi Sahina,

Can you please review the edited doc text for technical accuracy and sign off?
Comment 6 Sahina Bose 2014-12-24 09:11:29 UTC 
Minor edit done - otherwise looks good
Comment 7 Pavithra 2014-12-24 09:16:08 UTC 
Made a minor edit.
Comment 9 errata-xmlrpc 2015-01-15 13:48:08 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/RHBA-2015-0039.html
Note You need to log in before you can comment on or make changes to this bug.