Bug 1089636
Summary: | [Nagios] Cluster status information says "None of the volumes are in critical state" even when a volume is utilized beyond critical level. | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Shruti Sampat <ssampat> |
Component: | gluster-nagios-addons | Assignee: | Nishanth Thomas <nthomas> |
Status: | CLOSED CANTFIX | QA Contact: | RHS-C QE <rhsc-qe-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rhgs-3.0 | CC: | asriram, nthomas, sabose, sankarshan |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
In the Nagios UI, incorrect status information is displayed as "Cluster Status OK : None of the Volumes are in Critical State", when volume is utilized beyond critical level.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-01-30 11:12:16 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-04-21 09:55:01 UTC
The performance data for the cluster also shows the number of volumes in critical state as zero - noOfVolumesInCriticalState=0 As per the current design, cluster status is determined from the status of 'Volume Status' services of all the volumes under that cluster. The 'Cluster Utilization' service will reflect if any of volume's utilization goes beyond critical level. When the cascading gets implemented(in future) the cluster utilization service's will get propagated to cluster status This is inline with the implementation of volume Status as well. Similarly we don't consider the Brick Utilization while determining the Volume status. So as per my opinion this is not a bug and works as per the design As discussed in the triage meeting : we will take it up in the 3.1 release Please review and signoff edited doc text. Doctext is fine What would be the expected behavior? - Cluster status will be aggregation of status of all volumes or - Cluster status will be aggregation of both status and utilization of volumes 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. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |