Bug 1128082 - [Nagios] Improve quorum service status information when quorum is set on a volume for the first time.
Summary: [Nagios] Improve quorum service status information when quorum is set on a vo...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: gluster-nagios-addons
Version: rhgs-3.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Sahina Bose
QA Contact: RHS-C QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-08 09:25 UTC by Shruti Sampat
Modified: 2018-01-30 11:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-30 11:48:01 UTC


Attachments (Terms of Use)

Description Shruti Sampat 2014-08-08 09:25:45 UTC
Description of problem:
------------------------

When quorum is set on a volume for the first time, the status of the quorum service for the cluster reads "QUORUM: Server quorum regained for volume <vol-name>. Starting local bricks."

It would make more sense to display something like - ""
QUORUM: Server quorum turned on for volume <vol-name>

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

How reproducible:
Always

Steps to Reproduce:
1. Start monitoring a cluster of RHS nodes using Nagios, which has a distributed-replicate volume.
2.  Once all the services for the volume come up, set the quorum type to server on the volume.

Actual results:
The quorum status service displays the following message - "QUORUM: Server quorum regained for volume <vol-name>. Starting local bricks."

Expected results:
Might be better to display that quorum was turned on for the volume instead of using the word "regained".

Additional info:

Comment 5 Sahina Bose 2018-01-30 11:48:01 UTC
Thank you for your bug report. However, this bug is being closed as it's on a component where no further new development is being undertaken.


Note You need to log in before you can comment on or make changes to this bug.