Bug 1312207
Summary: | RFE: Add self-heal monitoring nagios plugin | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Sahina Bose <sabose> |
Component: | nagios-server-addons | Assignee: | Sahina Bose <sabose> |
Status: | CLOSED ERRATA | QA Contact: | Sweta Anandpara <sanandpa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rhgs-3.1 | CC: | bugs, divya, rcyriac, rhinduja, sabose, smohan |
Target Milestone: | --- | Keywords: | FutureFeature, ZStream |
Target Release: | RHGS 3.1.3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | nagios-server-addons-0.2.4-1 | Doc Type: | Enhancement |
Doc Text: |
A Nagios plugin has been added to monitor if a replicate volume has entries that are not in sync with other bricks of the replica set. Now, administrators can ensure that they do not perform maintenance actions when there are pending heals, and can also monitor the heal progress by viewing the trending information on entries to be healed.
|
Story Points: | --- |
Clone Of: | 1267586 | Environment: | |
Last Closed: | 2016-06-23 05:27:39 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: | 1267586 | ||
Bug Blocks: | 1258386, 1311386, 1320438 |
Description
Sahina Bose
2016-02-26 05:58:28 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions Tested and verified this on the build nagios-server-addons 0.2.4-1 and gluster-server 3.7.9-2 The sanity check on the new service 'volume Heal info' and the corresponding 'Volume Split-brain status' is complete. New BZs are raised for issues faced while executing the test cases in and around this area. Moving this RFE to fixed in 3.1.3 acked 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://access.redhat.com/errata/RHBA-2016:1242 |