Description of problem: If the users chooses to enable monitoring again, after disabling it, he/she should be able to do it. And that should bring back the Trends tab in the RHSC UI and Nagios server should start running and it's UI should respond. Above is the Acceptance Critieria for the feature which was designed. However, currently there is No option provided to RE-ENABLE Nagios Monitoring either from RHSC UI or from CLI, after disabling it once. Version-Release number of selected component (if applicable): rhsc-3.0.0-0.11.el6_5.noarch rhsc-monitoring-uiplugin-0.1.0-3.el6rhs.noarch How reproducible: 100% Steps to Reproduce: 1. Install and setup RHSC + Nagios Server using http://rhsm.pad.engineering.redhat.com/rhsc-nagios-release-denali-8 with Monitoring enabled. 2. Disable Monitoring from UI or from CLI once Bug 1111079 is fixed. 3. Now try to re-enable Monitoring Actual results: No option provided to RE-ENABLE Nagios Monitoring either from RHSC UI or from CLI, after disabling it once Expected results: As described in the Acceptance Critieria, there should be an option available to re-enable Nagios Monitoring either from RHSC UI or using script or both. Additional info:
We should document the steps how to enable and disable monitoring feature in RHSC using the back-end flags. All the steps should be clearly documented.
Please review the edited doc text and signoff.
doc-text looks fine
Use the command "rhsc-monitoring enable" from command line to re-enable already disabled monitoring feature in RHSC.
Verified as fixed in rhsc-setup-plugins-3.0.1-1.0.el6rhs.noarch After monitoring is disabled, it can be enabled by running the following command - # rhsc-monitoring enable Setting the monitoring flag... Starting nagios: done. Starting nsca: [ OK ] INFO: Move the nodes of existing cluster (with compatibilty version >= 3.4) to maintenance and re-install them. This would enable the monitoring for the cluster. After this, the UI page needs to be refreshed and the trends tab is seen again. Nagios server and NSCA services are started again.
Hi Shubhendu, Can you please review the edited doc text for technical accuracy and sign off?
Looks fine
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-0039.html