Description of problem: Most of the users would have configured mail notifications in their nagios settings, triggering a mail to be sent to their mentioned email contact when the server status goes to warning/critical. The current documented way of enabling mail services, is to make an entry in two files: i) /etc/nagios/gluster/gluster-contacts.cfg ii) /etc/nagios/gluster/gluster-templates.cfg Update to nagios-server-addons 0.2.4-1 (which involves a change in /etc/nagios/gluster/gluster-templates.cfg), creates a new file, when it figures out the original file is modified. The new file that gets created is /etc/nagios/gluster/gluster-templates.cfg.rpmnew Yum update succeeds (albeit a warning), and we don't see the new changes as the old file /etc/nagios/gluster/gluster-templates.cfg continues to be used. This bug is to figure out the best way to let the customers update to the newer build, thereby limiting the scope of missed warnings. Version-Release number of selected component (if applicable): glusterfs-3.7.9-1.el7rhgs.x86_64 How reproducible: Always Steps to Reproduce: 1. Have a cluster, with nagios-server-addons package 0.2.3-1 2. Configure mail notification as mentioned in the admin guide 3. Update to nagios-server-addons 0.2.4-1 4. Verify if the update is successful. Login to the nagios web UI and verify if we see 'volume self heal info' - one of the changes that is new is 0.2.4-1 Verify if two gluster-templates.cfg files are present in /etc/nagios/gluster/ Additional info: [root@dhcp47-188 gluster]# [root@dhcp47-188 gluster]# rpm -qa | grep gluster glusterfs-api-3.7.9-1.el7rhgs.x86_64 glusterfs-libs-3.7.9-1.el7rhgs.x86_64 glusterfs-api-devel-3.7.9-1.el7rhgs.x86_64 vdsm-gluster-4.16.30-1.3.el7rhgs.noarch glusterfs-3.7.9-1.el7rhgs.x86_64 glusterfs-cli-3.7.9-1.el7rhgs.x86_64 glusterfs-geo-replication-3.7.9-1.el7rhgs.x86_64 gluster-nagios-common-0.2.4-1.el7rhgs.noarch glusterfs-client-xlators-3.7.9-1.el7rhgs.x86_64 glusterfs-server-3.7.9-1.el7rhgs.x86_64 glusterfs-rdma-3.7.9-1.el7rhgs.x86_64 glusterfs-devel-3.7.9-1.el7rhgs.x86_64 gluster-nagios-addons-0.2.6-1.el7rhgs.x86_64 glusterfs-fuse-3.7.9-1.el7rhgs.x86_64 [root@dhcp47-188 gluster]# [root@dhcp47-188 gluster]# [root@dhcp47-188 gluster]# [root@dhcp47-188 gluster]# gluster v list nash ozone [root@dhcp47-188 gluster]# [root@dhcp47-188 gluster]# ls -l /etc/nagios/gluster/ total 40 drwxr-xr-x. 2 root root 59 Apr 11 16:02 default -rw-r--r--. 1 root root 5081 Apr 5 14:55 gluster-commands.cfg -rw-r--r--. 1 root root 1564 Apr 5 11:11 gluster-contacts.cfg -rw-r--r--. 1 root root 241 Apr 5 14:55 gluster-host-groups.cfg -rw-r--r--. 1 root root 2399 Apr 5 14:55 gluster-host-services.cfg -rw-r--r--. 1 root root 2544 Apr 5 11:11 gluster-templates.cfg -rw-r--r--. 1 root root 2671 Apr 5 14:55 gluster-templates.cfg.rpmnew -rw-r--r--. 1 root root 19 Apr 5 14:55 host-monitoring-services.in -rw-r--r--. 1 root nagios 133 Apr 5 14:55 snmpmanagers.conf drwxr-xr-x. 2 root root 4096 Apr 18 11:07 vm14_rhel7313 [root@dhcp47-188 gluster]# [root@dhcp47-188 gluster]#
Will move the new config for self-heal info monitoring to a new config file to avoid this issue
http://review.gluster.org/14072 posted
Tested and verified this on the build glusterfs-server 3.7.9-4 and nagios-server-addons-0.2.5-1 Installed RHGS 3.1.2 build (which comes with nagios-server-addons 0.2.3-1), with mail notification configured. Created replica volume(s) and updated the glusterfs-server build as well as nagios-server-addons (as mentioned above). Ran 'configure-gluster-nagios' again, which prompted for a new service 'volume-heal-info' to be added for every replica volume. The change was correctly seen in the nagios web UI. A new file gluster-templates-additions.cfg is present in /etc/nagios/gluster/ , as expected. Moving this bug to verified in 3.1.3.
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