Bug 1699835

Summary:	Glusterd did not start by default after node reboot
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Sayalee <saraut>
Component:	glusterd	Assignee:	Mohit Agrawal <moagrawa>
Status:	CLOSED ERRATA	QA Contact:	Kshithij Iyer <kiyer>
Severity:	high	Docs Contact:
Priority:	high
Version:	rhgs-3.5	CC:	amukherj, kiyer, moagrawa, rhinduja, rhs-bugs, sasundar, storage-qa-internal, ubansal, vbellur
Target Milestone:	---	Keywords:	Regression
Target Release:	RHGS 3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0-2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1700656 (view as bug list)		Environment:
Last Closed:	2019-10-30 12:20:51 UTC	Type:	Bug
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:
Bug Blocks:	1696807, 1700656

Description Sayalee 2019-04-15 10:48:14 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).

Additional info:
sos-reports will be shared

Comment 3 SATHEESARAN 2019-04-15 14:38:43 UTC

Sayalee,

I presume that the glusterd service is not enabled across reboots

<snip>
   Loaded: loaded (/usr/lib/systemd/system/glusterd.service; disabled; vendor preset: disabled)
</snip>

Could you check # systemctl is-enabled glusterd ?

Comment 6 SATHEESARAN 2019-04-16 06:45:01 UTC

(In reply to Upasana from comment #5)
> (In reply to SATHEESARAN from comment #3)
> > Sayalee,
> > 
> > I presume that the glusterd service is not enabled across reboots
> > 
> > <snip>
> >    Loaded: loaded (/usr/lib/systemd/system/glusterd.service; disabled;
> > vendor preset: disabled)
> > </snip>
> > 
> > Could you check # systemctl is-enabled glusterd ?
> 
> Hi Sas,
> 
> I too have seen the issue.
> Yes it is not enabled across reboots
> [root@ ~]# systemctl is-enabled glusterd
> disabled
> [root@ ~]# 
> [root@ ~]# systemctl enable glusterd
> Created symlink from
> /etc/systemd/system/multi-user.target.wants/glusterd.service to
> /usr/lib/systemd/system/glusterd.service.
> 
> After enabling it glusterd is coming up post reboot


Thanks, this means that the glusterd is not enabled across reboots. This is the issue to be sorted out.

Comment 20 errata-xmlrpc 2019-10-30 12:20:51 UTC

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://access.redhat.com/errata/RHEA-2019:3249