+++ 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):
3.0
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 Nagaprasad Sathyanarayana on 2014-09-12 02:18:44 EDT ---
When these BZs were deferred from 3.0 release, they were marked to be triaged in 3.0.1 release. Since 3.0.1 is now the Zero day errata (which are tracked with Target Milestone=3.0.1, Internal Whiteboard=Denali 0day), changing the target milestone of these to 3.0.2. Engineers still must triage these BZs and pull only the feasible ones into 3.0.2 release.
--- Additional comment from RamaKasturi on 2014-11-20 06:54:06 EST ---
When host is added to console glusterpmd is started. But when user tries to reboot the system and once the system comes back, user has to manual start it. The reason being chkconfig for glusterpmd is not on.
So, moving this bug back.