Bug 1324655

Summary:	No instruction to enable the pacemaker services
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Dustin Black <dblack>
Component:	doc-Administration_Guide	Assignee:	Bhavana <bmohanra>
doc-Administration_Guide sub component:	Default	QA Contact:	Shashank Raj <sraj>
Status:	CLOSED CURRENTRELEASE	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	akhakhar, asriram, asrivast, bmohanra, dblack, jthottan, kkeithle, mhideo, ndevos, nlevinki, rcyriac, rhinduja, rhs-bugs, rwheeler, sashinde, skoduri, sraj, storage-doc
Version:	rhgs-3.1	Keywords:	ZStream
Target Milestone:	---
Target Release:	RHGS 3.1.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-11 17:28:33 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:	1329186

Description Dustin Black 2016-04-06 21:26:11 UTC

Document URL: 
https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Administration_Guide/sect-NFS.html

Section Number and Name: 
7.2.3.x

Describe the issue: 
The `gluster nfs-ganesha enable` command will in fact start the nfs-ganesha and pacemaker services, so at runtime everything will begin operating as expected. However, on a reboot neither the nfs-ganesha nor the pacemaker services start as they have not been enabled with systemctl or chkconfig, so the cluster does not start and NFS does not serve exports. The nfs-ganesha and pacemaker services should be enabled with systemctl to ensure the services survive a reboot.

Suggestions for improvement: 
Add instructions to enable these services. With RHEL 7:

systemctl enable nfs-ganesha.service
systemctl enable pacemaker.service


Additional information:

Comment 2 Soumya Koduri 2016-04-07 17:40:15 UTC

BZ1236017 captures the discussions we had to some extent with respect to nfs-ganesha service not starting by default. Do we still need to document to enable the service by default or leave it to admin to decide?

Comment 3 Dustin Black 2016-04-07 18:24:08 UTC

Thanks Soumya!

The conversation in BZ1236017 does cover the question of the nfs-ganesha service, but not the pacemaker service, which the docs also do not say to enable.

Without the pacemaker service enabled at boot time, the cluster will not form and starting the nfs-ganesha service will not result in the VIP failing back to the node.

Comment 4 Dustin Black 2016-04-07 18:25:24 UTC

I've edited the title to reflect that we only need to update the docs for the pacemaker service and not the nfs-ganesha service.

Comment 5 Soumya Koduri 2016-04-07 18:38:53 UTC

(In reply to Dustin Black from comment #3)
> Thanks Soumya!
> 
> The conversation in BZ1236017 does cover the question of the nfs-ganesha
> service, but not the pacemaker service, which the docs also do not say to
> enable.
> 
> Without the pacemaker service enabled at boot time, the cluster will not
> form and starting the nfs-ganesha service will not result in the VIP failing
> back to the node.

Right. Thanks for the update.

Comment 6 Bhavana 2016-04-19 10:03:22 UTC

An additional bullet point is added to enable pacemaker under "7.2.3.3.1. Prerequisites to run NFS-Ganesha".

*Enable the pacemaker service using the following command:
For Red Hat Enterprise Linux 6:

# chkconfig --add pacemaker
# chkconfig pacemaker on

For Red Hat Enterprise Linux 7:

# systemctl enable pacemaker.service

Dustin,

I have added the command for RHEL 6 too. Can you let me know if both the commands are necessary or should i remove " # chkconfig pacemaker on".


http://jenkinscat.gsslab.pnq.redhat.com:8080/job/doc-Red_Hat_Gluster_Storage-3.1-3.1.2-Stage_Administration_Guide%20%28html-single%29/lastSuccessfulBuild/artifact/tmp/en-US/html-single/index.html#sect-NFS_Ganesha

Comment 7 Dustin Black 2016-04-19 13:46:36 UTC

Looks good.

Comment 8 Bhavana 2016-04-20 06:10:17 UTC

Moving the bug on_qa.

Comment 10 Shashank Raj 2016-04-27 14:29:01 UTC

Verified this bug on both RHEL 6 and RHEL 7 platform by enabling the pacemaker service, as mentioned in the doc, using below commands

For Red Hat Enterprise Linux 6:

# chkconfig --add pacemaker
# chkconfig pacemaker on

For Red Hat Enterprise Linux 7:

# systemctl enable pacemaker.service

http://10.34.3.139:8080/view/Gluster/job/doc-Red_Hat_Gluster_Storage-3.1.2-Administration_Guide%20%28html-single%29/ws/tmp/en-US/html-single/index.html#sect-NFS_Ganesha

After reboot, pacemaker service was started automatically.

based on the document content and verified steps, marking this bug as Verified.