Bug 1236556 - Ganesha volume export failed
Summary: Ganesha volume export failed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: nfs-ganesha
Version: rhgs-3.1
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: ---
: RHGS 3.1.0
Assignee: Meghana
QA Contact: Apeksha
URL:
Whiteboard:
Depends On: 1236561 1236933
Blocks: 1202842
TreeView+ depends on / blocked
 
Reported: 2015-06-29 12:29 UTC by Apeksha
Modified: 2015-09-01 02:54 UTC (History)
8 users (show)

Fixed In Version: glusterfs-3.7.1-7.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1236561 (view as bug list)
Environment:
Last Closed: 2015-07-29 05:08:22 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1495 0 normal SHIPPED_LIVE Important: Red Hat Gluster Storage 3.1 update 2015-07-29 08:26:26 UTC

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


Note You need to log in before you can comment on or make changes to this bug.