Bug 1512609
| Summary: | [GSS][RHEL-6] new PID file location is not known to nagios, causing inaccurate reporting | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Sahina Bose <sabose> |
| Component: | gluster-nagios-addons | Assignee: | Sahina Bose <sabose> |
| Status: | CLOSED ERRATA | QA Contact: | Sweta Anandpara <sanandpa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.3 | CC: | amukherj, asrivast, ccalhoun, dnarayan, ndevos, pmulay, pousley, rcyriac, rhinduja, rhs-bugs, sabose, sanandpa, storage-qa-internal |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | RHGS 3.3.1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | gluster-nagios-addons-0.2.10-2 | Doc Type: | If docs needed, set a value |
| Doc Text: |
Gluster brick process monitoring does not account for the new location of the brick process file. With this update, nagios monitoring checks the correct location of gluster brick PID file.
|
Story Points: | --- |
| Clone Of: | 1498112 | Environment: | |
| Last Closed: | 2017-11-29 03:23:15 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: | 1498112 | ||
| Bug Blocks: | 1475688 | ||
|
Comment 3
Sweta Anandpara
2017-11-14 05:02:21 UTC
Adding Doc text from associated BZ (https://bugzilla.redhat.com/show_bug.cgi?id=1498112) as provided by Sahina in Errata Advisory 30965 (https://errata.devel.redhat.com/docs/show/30965) Hi Sahina, I've edited the Doc Text for it's associated Errata. Request you to review the same and let me know in case of any concerns. If no changes are required, request you to provide your approval for the same. Yes - 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://access.redhat.com/errata/RHBA-2017:3271 |