Bug 1136207

Summary: [Nagios] Volume status service shows "All bricks are Up" even when some of the bricks are in unknown state
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Shruti Sampat <ssampat>
Component: gluster-nagios-addonsAssignee: Nishanth Thomas <nthomas>
Status: CLOSED CANTFIX QA Contact: RHS-C QE <rhsc-qe-bugs>
Severity: medium Docs Contact:
Priority: high    
Version: rhgs-3.0CC: asriram, nthomas, sankarshan
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
Volume status service shows "All bricks are Up" message even when some of the bricks are in UNKNOWN state due to unavailability of glusterd process.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-01-30 11:11:45 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    

Description Shruti Sampat 2014-09-02 07:33:07 UTC
Description of problem:
-----------------------

When glusterd is stopped on one of the nodes in the cluster, the bricks residing on the node are seen to be unknown. For the volume whose bricks are unknown, the volume status service is seen to be OK with the status information as "OK: Volume : DISTRIBUTE type - All bricks are Up". This seems misleading as some of the bricks are in unknown status.

Version-Release number of selected component (if applicable):
-------------------------------------------------------------

gluster-nagios-addons-0.1.10-2.el6rhs.x86_64
nagios-server-addons-0.1.6-1.el6rhs.noarch

How reproducible:
Saw it once.

Steps to Reproduce:

1. Setup a cluster of 4 RHS nodes and configure it to be monitored nagios server that is setup outside the RHS cluster.

2. Create a distribute volume with one brick each on 2 of the servers in the cluster.

3. Bring down glusterd on one of the nodes in the cluster, this node should have one of the bricks created above.

4. Observe the volume status service for this volume. 

Actual results:
The volume status service appears to be flapping between OK, warning and unknown states (BZ #1136205)

The status information of the service when it is OK is "OK: Volume : DISTRIBUTE type - All bricks are Up"

Expected results:

The status information of the volume status should not display that all bricks are up as some bricks are in unknown state. 

Additional info:

Comment 3 Shalaka 2014-09-20 16:58:50 UTC
Please review and sign-off edited doc text.

Comment 4 Ramesh N 2014-09-25 11:44:57 UTC
Moving out of RHS 3.0.2

Comment 5 Sahina Bose 2018-01-30 11:11:45 UTC
Thank you for your report. However, this bug is being closed as it's logged against gluster-nagios monitoring for which no further new development is being undertaken.