+++ This bug was initially created as a clone of Bug #1138198 +++
+++ This bug was initially created as a clone of Bug #1138108 +++
Description of problem:
When monitoring via Nagios is enabled, the host installation flow should make sure that the glusterpmd service is running on the newly added host. (Similar to the nrpe configuration that takes place on the host)
Version-Release number of selected component (if applicable):
How reproducible:
Always
Actual results:
Currently, glusterpmd service needs to be started manually on the host. This service monitors the gluster related processes and sends notification to Nagios server.
Expected results:
Service is started automatically.
Additional info:
--- Additional comment from Alon Bar-Lev on 2014-09-04 05:56:37 EDT ---
what is the action item?
--- Additional comment from Darshan on 2014-09-04 06:12:49 EDT ---
(In reply to Alon Bar-Lev from comment #1)
> what is the action item?
having a plugin under gluster which would start the glusterpmd service if monitoring is enabled.
--- Additional comment from Itamar Heim on 2014-09-07 04:01:19 EDT ---
sahina - please set target release
--- Additional comment from Sandro Bonazzola on 2014-10-17 08:23:20 EDT ---
oVirt 3.5 has been released and should include the fix for this issue.
This bug is not relevant for RHEV-M as the monitoring via Nagios is not enabled for RHS nodes here unlike in RHSC (RHSC ships Nagios and asks if monitoring needs to be enabled during setup)
Verification of glusterpmd auto-start during host-deploy will not be possible in RHEV-M.