+++ This bug was initially created as a clone of Bug #1384756 +++ Description of problem: ======================= There is already a BZ for making glusterfs-events package optional, as not all our users will be requiring it. IF there is a need for eventing feature, a user is going to explicitly download and install glusterfs-events. When that is done, there is no point of having an added-on step to explicitly enable glustereventsd service. Like how glusterd service is enabled by default when we install glusterfs-server, it would ease out usability if glustereventsd is enabled by default when glusterfs-event package is installed. How reproducible: ================== Always Steps to Reproduce: ==================== 1. Have a 2/4 node cluster and install glusterfs-server, with glusterfs-events rpm 2. Check if glustereventsd is enabled and running. Actual results: ============== glustereventsd service is neither enabled nor running Expected results: ================ glustereventsd service should be enabled and running
REVIEW: http://review.gluster.org/15853 (eventsapi: Enable and start glustereventsd on install) posted (#1) for review on master by Aravinda VK (avishwan)
Fedora packaging guidelines suggest not to enable a service by default after installation. Closing this bug as this is the expected behavior. Please reopen if this is still a issue.