Description of problem: ------------------------ After updating gluster-nagios-addons package, user is required to restart nrpe service manually. It would be better if the package takes care of reloading nrpe service after the update. Version-Release number of selected component (if applicable): -------------------------------------------------------------- gluster-nagios-addons-0.1.16-1.el6rhs.x86_64 How reproducible: ----------------- Always Steps to Reproduce: -------------------- 1. Update gluster-nagios-addons on a RHSS node being monitored. Actual results: --------------- nrpe service needs to be restarted manually. Expected results: ----------------- nrpe reload can be performed automatically after the package update. Additional info:
Kanagaraj, I see this added as a known issue in the 3.0.4 Known Issues tracker bug. Could you please fill out the doc text?
Hi Kanagaraj, Could you please review the edited doc text and sign off?
Can u change the sentence "A few changes in the nrpe.cfg file has resulted in the nrpe service not reloading when the gluster-nagios-addons package is updated" to "A few changes in the nrpe.cfg file requires reloading of nrpe service when the gluster-nagios-addons package is updated but its done during update".
I've made the edit. Can you please review?
Doc text looks good.
This bug was fixed as part of the fix for bz#1106421. NRPE service will be restarted on every upgrade if the service is already running.
Moving it to ON_QA to be verified as per comment 7
Verified and works fine with build gluster-nagios-addons-0.2.4-4.el6rhs.x86_64. Confirmed that nrpe gets reloaded after upgradating gluster-nagios-addons by looking at its PID file.
Hi Ramesh, The doc text is updated. Please review it and share your technical review comments. If it looks ok, then sign-off on the same.
Doc text looks good. Approved.
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-1848.html