Bug 1119189 - [Nagios] - When glusterd is stopped on all the nodes in a cluster, volume status displays status as 'UNKNOWN' and status information as "Command execution failed command execution failed"
Summary: [Nagios] - When glusterd is stopped on all the nodes in a cluster, volume sta...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: nagios-server-addons
Version: rhgs-3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Sahina Bose
QA Contact: RHS-C QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-14 08:52 UTC by RamaKasturi
Modified: 2018-01-30 11:47 UTC (History)
1 user (show)

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

Attachments (Terms of Use)
Attaching screenshot for volume status when glusterd is down on all the nodes. (335.98 KB, image/png)
2014-07-14 08:53 UTC, RamaKasturi 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description RamaKasturi 2014-07-14 08:52:19 UTC 
Description of problem:
status and statusinformation of volume status service displays "UNKNOWN" and "UNKNOWN: Command execution failed command execution failed".

Version-Release number of selected component (if applicable):
nagios-server-addons-0.1.5-1.el6rhs.noarch

How reproducible:
Always

Steps to Reproduce:
1. Install nagios on RHS nodes.
2. Setup a cluster with volumes in it.
3. Now kill glusterd on all the nodes inside the cluster.

Actual results:
Volume status information shows "UNKNOWN: Command execution failed command execution failed".

Expected results:
Volume status information should display "UNKOWN: Command execution failed".

Additional info:
Comment 1 RamaKasturi 2014-07-14 08:53:36 UTC 
Created attachment 917703 [details]
Attaching screenshot for volume status when glusterd is down on all the nodes.
Comment 7 Sahina Bose 2018-01-30 11:47:13 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.