Red Hat Bugzilla – Bug 1121009
[Nagios] - [RFE] - Auto discovery creates ctdb related nagios services though it is not configured.
Last modified: 2018-08-14 07:15:59 EDT
Description of problem: Auto Discovery create ctdb related nagios service though it is not configured in nagios. Version-Release number of selected component (if applicable): gluster-nagios-addons-0.1.8-1.el6rhs.x86_64 How reproducible: Always. Steps to Reproduce: 1. Install nagios on RHS nodes. 2. Now create a cluster and run discovery.py script. 3. Actual results: Auto discovery creates ctdb related nagios services though it is not configured. Expected results: Auto discovery should not create ctdb related nagios services if it is not configured. Additional info:
This should be documented, so that the customer does not get confused by seeing the ctdb related services in Nagios monitoring. Though, there is not a clear way to figure out how to avoid this, but we have to find out a way to address this in 3.0.z
In RHS, ctdb is not installed by default. It is installed and setup by the user on a need basis. So during the discovery, need to check whether ctdb is setup or not and make the decision based on that. This can be done by checking for clustering = yes idmap backend = tdb2 parameters in the /etc/smb/smb.conf. These entries are added/removed by the gluster hooks(/var/lib/glusterd/hooks/1/start/post/S29CTDBsetup.sh and var/lib/glusterd/hooks/1/stop/pre/S29CTDB-teardown.sh) while start/stop the meta volume
Moving out of RHS 3.0.2.
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.