Description of problem: ------------------------- On running `rhsc-setup' command, the nagios service is started by executing `service nagios start'. This can cause a problem if the Nagios service is already running (in case of an upgrade). It would be better to execute restart of nagios service instead of start. This issue causes all cluster level services to be in warning state with "null" status information after an upgrade from RHSC 3.0.3 to RHSC 3.0.4 Version-Release number of selected component (if applicable): -------------------------------------------------------------- rhsc-setup-3.0.4-1.25.el6rhs.noarch How reproducible: ------------------- Frequently Steps to Reproduce: ------------------- 1. Setup RHSC 3.0.3 with Nagios monitoring 2. Upgrade RHSC, Nagios and the RHSS nodes to 3.0.4 3. Observe the Cluster services after upgrade. Actual results: ---------------- Cluster services are seen to be in warning state with "null" status information. Expected results: ------------------ Cluster services are expected to be OK, or reflecting correct states instead of being in warning state. Additional info:
Verified as fixed in rhsc-setup-plugins-3.0.4-1.2.el6rhs.noarch Tested by upgrading from RHSC 3.0.3 to 3.0.4 without any issues. Cluster services behave as expected. Checked that livestatus works without any issues by running - # /usr/lib64/nagios/plugins/gluster/check_cluster_status.py <cluster-name> OK : None of the Volumes in the cluster are in Critical State No errors or exceptions seen in /var/log/messages Checked that nagios service is restarted after running `rhsc-setup' by comparing process id before and after running `rhsc-setup' command.
Please add doc text.
Setting requires_doc_text flag to "-" based on discussion with Ramesh and Shubhendu.
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://rhn.redhat.com/errata/RHBA-2015-0681.html