Bug 1236556

Summary:	Ganesha volume export failed
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Apeksha <akhakhar>
Component:	nfs-ganesha	Assignee:	Meghana <mmadhusu>
Status:	CLOSED ERRATA	QA Contact:	Apeksha <akhakhar>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	rhgs-3.1	CC:	amainkar, kkeithle, mmadhusu, ndevos, nlevinki, saujain, skoduri, vagarwal
Target Milestone:	---
Target Release:	RHGS 3.1.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.7.1-7.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1236561 (view as bug list)		Environment:
Last Closed:	2015-07-29 05:08:22 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:	1236561, 1236933
Bug Blocks:	1202842

Description Apeksha 2015-06-29 12:29:03 UTC

Description of problem:
Ganesha Volume export failed [regression]

Version-Release number of selected component (if applicable):
nfs-ganesha-2.2.0-3.el6rhs.x86_64
glusterfs-3.7.1-5.el6rhs.x86_64

How reproducible:
Once

Steps to Reproduce:
1. Set up an 8 node ganesha cluster
2. Create a 6X2 volume
3. Do a ganesha.enable on for the volume, it fails to export the volume

[root@vm1 ~]# gluster vol set testvol ganesha.enable on
volume set: failed: Dynamic export addition/deletion failed. Please see log file for details

Actual results: Ganesha Volume export failed


Expected results: =Ganesha volume must get exported


Additional info:

Comment 3 Meghana 2015-06-30 03:35:14 UTC

This is a critical functionality loss as ganesha export fails in a clean set up.
This wass introduced by one of the commits that went into the previous builds.
The fix is merged upstream and will be backported today.

Comment 5 Apeksha 2015-07-08 10:54:15 UTC

Ganesha volume gets exported

Comment 6 errata-xmlrpc 2015-07-29 05:08:22 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