Bug 1111087

Summary:	No option provided to RE-ENABLE Nagios Monitoring either from RHSC UI or from CLI, after disabling it once
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Prasanth <pprakash>
Component:	rhsc	Assignee:	Shubhendu Tripathi <shtripat>
Status:	CLOSED ERRATA	QA Contact:	Shruti Sampat <ssampat>
Severity:	medium	Docs Contact:
Priority:	high
Version:	rhgs-3.0	CC:	asrivast, dpati, nlevinki, psriniva, rhs-bugs, rhsc-qe-bugs, rnachimu, sharne, shtripat, ssampat
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.0.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhsc-setup-plugins-3.0.1-1.0.el6rhs	Doc Type:	Bug Fix
Doc Text:	Previously, there was no mechanism to enable the monitoring feature after disabling it. With this fix, the user can enable monitoring by executing 'rhsc-monitoring enable' command from the command line interface.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-15 13:48:36 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:	1111079
Bug Blocks:	1087818

Description Prasanth 2014-06-19 08:30:35 UTC

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:

Comment 1 Dusmant 2014-06-25 05:56:57 UTC

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.

Comment 2 Shalaka 2014-06-25 13:29:48 UTC

Please review the edited doc text and signoff.

Comment 3 Shubhendu Tripathi 2014-06-26 03:57:19 UTC

doc-text looks fine

Comment 5 Shubhendu Tripathi 2014-11-07 05:00:43 UTC

Use the command "rhsc-monitoring enable" from command line to re-enable already disabled monitoring feature in RHSC.

Comment 6 Shruti Sampat 2014-11-19 07:09:15 UTC

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.

Comment 7 Pavithra 2014-12-26 07:10:48 UTC

Hi Shubhendu,

Can you please review the edited doc text for technical accuracy and sign off?

Comment 8 Shubhendu Tripathi 2014-12-29 04:19:14 UTC

Looks fine

Comment 10 errata-xmlrpc 2015-01-15 13:48:36 UTC

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