Bug 1141171
| Summary: | [Nagios] Quorum service is seen to be OK when it should actually be in CRITICAL state | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Shruti Sampat <ssampat> |
| Component: | gluster-nagios-addons | Assignee: | Sahina Bose <sabose> |
| Status: | CLOSED ERRATA | QA Contact: | Shruti Sampat <ssampat> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | rhgs-3.0 | CC: | asrivast, dpati, psriniva, rhsc-qe-bugs, rnachimu, sabose, sgraf, sharne |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | RHGS 3.0.3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | gluster-nagios-addons-0.1.12-1.el6rhs | Doc Type: | Bug Fix |
| Doc Text: |
Previously, the status of the quorum service displayed an incorrect status. With this fix, a buffering issue is fixed and the quorum service displays the appropriate status.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-01-15 13:49:46 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: | |||
|
Description
Shruti Sampat
2014-09-12 11:33:44 UTC
The issue was due to buffered messages by the plugin that processes the syslog messages. This happens when the quorum is regained and lost again. The earlier message for quorum regained was in the buffer and resend to nagios when the quorum lost messages were received. This behaviour is fixed with the attached patch Verified as fixed in gluster-nagios-addons-0.1.12-1.el6rhs.x86_64 Quorum service remains in critical state when quorum is lost. Please add doc text for this bug. Hi Sahina, Can you please review the edited doc text for technical accuracy and sign off? Looks good 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 |