Bug 1452069
| Summary: | [CTDB] Nagios shows ctdb service as CRITICAL even when all nodes are healthy | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Sweta Anandpara <sanandpa> |
| Component: | ctdb | Assignee: | Anoop C S <anoopcs> |
| Status: | CLOSED ERRATA | QA Contact: | Sweta Anandpara <sanandpa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.3 | CC: | amukherj, anoopcs, rcyriac, rhinduja, rhs-bugs, rhs-smb |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | RHGS 3.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | samba-4.6.3-2.el7rhgs | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-09-21 04:47:10 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: | 1417151 | ||
|
Description
Sweta Anandpara
2017-05-18 09:30:30 UTC
Hi Sweta, Good catch. It's a bug in ctdb for which I have raised an upstream bug. This sneaked in while re-factoring ctdb code in v4.5. Judging from the nagios messages, I assume that it is trying to parse the displayed output of `ctdb nodestatus`. Instead it can also rely on the exit status after running `ctdb nodestatus` which reflects the health status of current node. This has been fixed upstream via the following commits: [1] https://git.samba.org/?p=samba.git;a=commit;h=a600d467e2842ab05e429c5a67be5b222ddd1c12 [2] https://git.samba.org/?p=samba.git;a=commit;h=1d10c8e9e637619b754b4a273d3c714fbca7d503 [3] https://git.samba.org/?p=samba.git;a=commit;h=ade535371b86294c12ca3f7eb98d8ef7ecd29caa Following the discussion we had in our team, moving the component to ctdb as it is a regression from previous version. Tested and verified this on the build samba-4.6.3-3.el7rhgs.x86_64, ctdb-4.6.3-3.el7rhgs.x86_64 and glusterfs-3.8.4-28.el7rhgs.x86_64 Ctdb nodestatus command (on CLI) gives the output of ctdb status only of the localhost (as expected). Nagios when configured displays the ctdb service as OK. Moving this to verified in 3.3. [root@dhcp47-121 ~]# ctdb status Number of nodes:6 pnn:0 10.70.47.113 OK pnn:1 10.70.47.114 OK pnn:2 10.70.47.115 OK pnn:3 10.70.47.116 OK pnn:4 10.70.47.117 OK pnn:5 10.70.47.121 OK (THIS NODE) Generation:368498462 Size:6 hash:0 lmaster:0 hash:1 lmaster:1 hash:2 lmaster:2 hash:3 lmaster:3 hash:4 lmaster:4 hash:5 lmaster:5 Recovery mode:NORMAL (0) Recovery master:4 [root@dhcp47-121 ~]# ctdb nodestatus pnn:5 10.70.47.121 OK (THIS NODE) [root@dhcp47-121 ~]# 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:2780 |