Bug 1224065

Summary:	gluster nfs-ganesha enable command failed
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Apeksha <akhakhar>
Component:	nfs-ganesha	Assignee:	Bug Updates Notification Mailing List <rhs-bugs>
Status:	CLOSED ERRATA	QA Contact:	Apeksha <akhakhar>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	rhgs-3.1	CC:	annair, asrivast, kkeithle, mmadhusu, nlevinki, saujain, skoduri
Target Milestone:	---
Target Release:	RHGS 3.1.0
Hardware:	x86_64
OS:	FreeBSD
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-29 04:45:30 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:	1202842

Description Apeksha 2015-05-22 07:04:47 UTC

Description of problem:
gluster nfs-ganesha enable command failed.
[root@nfs1 ~]# gluster nfs-ganesha enable
Enabling NFS-Ganesha requires Gluster-NFS to be disabled across the trusted pool. Do you still want to continue? (y/n) y
nfs-ganesha: failed: Failed to set up HA config for NFS-Ganesha. Please check the log file for details

Version-Release number of selected component (if applicable):
nfs-ganesha-2.2.0-0.el6.x86_64
glusterfs-3.7.0-2.el6rhs.x86_64

How reproducible:
once

Steps to Reproduce:
1. set up passwordless ssh for all nodes from all the servers.
2. update /etc/hosts/ in order to make hostname pingable, on all nodes.
3. remove files from /var/cache/rpcbind on all nodes.
4. service pcsd start, on all nodes.
5. use the command "passwd hacluster", and password being "hacluster", on all the nodes
6. update the /etc/ganesha.conf and /etc/ganesha/ganesha-ha.conf with necessary information.
7. mounted the shared volume on nodes
8. executed the command "gluster nfs-ganesha enable"

Actual results:gluster nfs-ganesha enable command fails

Expected results: gluster nfs-ganesha enable command should be a success

Additional info:ganesha process starts on all servers, but pcs errors out, looks like something to do with username "hacluster", assumption based on the logs mentioned below

/var/log/pcsd/pcsd.log :
[2015-05-21 21:56:33] INFO WEBrick::HTTPServer#start: pid=17101 port=2224
I, [2015-05-21T21:58:29.076346 #17101] INFO -- : ERROR: Request without authentication
::ffff:10.70.46.180 - - [21/May/2015 21:58:29] "GET /remote/check_auth HTTP/1.1" 401 24 0.0042

Comment 2 Apeksha 2015-05-22 10:24:26 UTC

We used pcs cluster command with all hostnames, for cluster to come up:

pcs cluster auth nfs1 -u hacluster -p hacluster

Please let us know if this has to be a manual step or it is automated in any of the scripts.

Comment 3 Meghana 2015-06-05 12:33:03 UTC

Apeksha, please  update the bug and close it if you can't reproduce the issue.

Comment 4 Soumya Koduri 2015-06-08 07:15:40 UTC

As discussed, 
'pcs cluster auth nfs1 -u hacluster -p hacluster' is a manual step.

Moving it to ON_QA for QE team to verify and test the setup. Please re-open in case if the issue still exists.

Comment 5 Apeksha 2015-06-26 08:52:51 UTC

Able to setup the ganesha 4 node cluster, gluster nfs-ganesha enable command was a success after executing manual step - 'pcs cluster auth nfs1 -u hacluster -p hacluster' on all the servers

Comment 6 errata-xmlrpc 2015-07-29 04:45:30 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://rhn.redhat.com/errata/RHSA-2015-1495.html