Description of problem: -------------------------- Consider rhsc-setup to be run with monitoring disabled. At a later point, monitoring was enabled using the command - # rhsc-monitoring enable Now consider that rhsc-setup was updated to a later version and rhsc-setup is run again. This time, instead of keeping monitoring turned on as expected, it disables monitoring as part of setup (as it was disabled when rhsc-setup was initially run) So, after running rhsc-setup after update, the status of monitoring is as follows - # rhsc-monitoring status RHSC monitoring is not enabled. Nagios is running NSCA is running Version-Release number of selected component (if applicable): -------------------------------------------------------------- rhsc-3.0.3-1.19.el6rhs.noarch How reproducible: ------------------- Always Steps to Reproduce: -------------------- 1. Run rhsc-setup and configure monitoring to be disabled. 2. Enable monitoring using the command - # rhsc-monitoring enable The status of monitoring is now - # rhsc-monitoring status RHSC monitoring is enabled. Nagios is running NSCA is running 3. Update the rhsc-setup package and run # rhsc-setup again. Actual results: ---------------- Monitoring is disabled as part of rhsc-setup. Expected results: ------------------ Monitoring should be configured as per current setting and should not depend on how it was setup initially using rhsc-setup. So in this case it should be enabled after running rhsc-setup following update. Additional info:
To be documented for 3.0.3 release.
Hi Shubhendu, Can you please verify the technical accuracy of the doc text and sign off?
I have modified the doc-text a bit. Kindly check once and re-phrase if required.
Looks good.
Made an edit.
With the current implementation, when running "rhsc-monitoring enable" it updates a json file. However, the value chosen during setup is not updated. Is it ok to ask the question regarding enabling monitoring again during upgrade?
I think that should be fine.
Fixed to override the answer file value in case the rhsc-monitoring json file is configured
As per Comment 8 and reviews on the patch, the flow has been changed to ask the user if monitoring needs to be enabled, on every run of rhsc-setup.
Verified as fixed in rhsc-setup-plugins-3.0.4-1.1.el6rhs Tested with upgrade from RHSC 3.0.3 installation to this version. `rhsc-setup' asks the user if monitoring needs to be enabled on every run.
Please review and sign-off edited doc text.
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