Bug 1700656

Summary:	Glusterd did not start by default after node reboot
Product:	[Community] GlusterFS	Reporter:	Mohit Agrawal <moagrawa>
Component:	glusterd	Assignee:	Mohit Agrawal <moagrawa>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	bmekala, bugs, moagrawa, rhinduja, rhs-bugs, sankarshan, saraut, sasundar, storage-qa-internal, ubansal, vbellur
Target Milestone:	---	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1699835	Environment:
Last Closed:	2019-04-17 11:53:36 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1699835
Bug Blocks:

Comment 1 Worker Ant 2019-04-17 05:50:50 UTC

REVIEW: https://review.gluster.org/22584 (spec: Glusterd did not start by default after node reboot) posted (#1) for review on master by MOHIT AGRAWAL

Comment 3 SATHEESARAN 2019-04-17 06:45:24 UTC

Description of problem:
Did reboot on a server node, but glusterd process was not started automatically after node reboot. When checked the glusterd status it was shown as inactive(dead), but on doing glusterd start, the process was active again.

Version-Release number of selected component (if applicable):
6.0-1

How reproducible:
Always

Steps to Reproduce:
1. Do reboot on a server node.
2. After the node is back up again, check the glusterd status using "systemctl status glusterd"
3. To start the glusterd process, do "systemctl start glusterd".

Actual results:
* When a server node is rebooted, and the node is back up online again, the glusterd service on the node does not start automatically.
* Glusterd has to started using "systemctl start glusterd".

Expected results:
On rebooting a node, when the node comes back up online, glusterd should be active(running).

Comment 4 Mohit Agrawal 2019-04-17 11:53:36 UTC

This is not a bug, it is expected behaviour.

Services are not allowed to get automatically enabled through RPM
scriptlets. Distributions that want to enable glusterd by default should
provide a systemd preset as explained in
https://www.freedesktop.org/wiki/Software/systemd/Preset/ . so closing the same.

Thanks,
Mohit Agrawal