Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1239057 - ganesha volume export fails in rhel7.1
ganesha volume export fails in rhel7.1
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: nfs-ganesha (Show other bugs)
3.1
All Linux
high Severity high
: ---
: RHGS 3.1.0
Assigned To: Meghana
Apeksha
:
Depends On:
Blocks: 1202842 1241480 1241885
  Show dependency treegraph
 
Reported: 2015-07-03 07:48 EDT by Apeksha
Modified: 2015-07-29 01:09 EDT (History)
11 users (show)

See Also:
Fixed In Version: glusterfs-3.7.1-9
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1241480 (view as bug list)
Environment:
Last Closed: 2015-07-29 01:09:17 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1495 normal SHIPPED_LIVE Important: Red Hat Gluster Storage 3.1 update 2015-07-29 04:26:26 EDT

  None (edit)
Description Apeksha 2015-07-03 07:48:30 EDT
Description of problem:
ganesha volume export fails in rhel7.1 with permissive mode

Version-Release number of selected component (if applicable):
selinux-policy-3.13.1-30.el7.noarch
glusterfs-3.7.1-7.el7rhgs.x86_64
nfs-ganesha-2.2.0-3.el7rhgs.x86_64

How reproducible:
Always

Steps to Reproduce:
1. set selinux to permisive mode
2. setup the ganesha cluster
3. now set ganesha.enable on, on the volume, it fails

[root@dhcp37-133 ~]# gluster v set nfsvol ganesha.enable on
volume set: failed: Failed to create NFS-Ganesha export config file.

Actual results: volume does not get exported


Expected results: Volume must get exported 


Additional info: Did not see any avc errors for this operation, running this in permissive mode since we are waiting for avc fixes for rhel7.1
Comment 3 Meghana 2015-07-07 00:10:14 EDT
A file that is used to identify the ganesha config file, "/etc/sysconfig/ganesha" is written
differently on RHEL 7.1. This leads to exports failing all the time on RHEL 7.1.
One of the scripts that ceates the export config file needs modification.
Comment 5 Niels de Vos 2015-07-07 11:15:36 EDT
(In reply to Meghana from comment #3)
> A file that is used to identify the ganesha config file,
> "/etc/sysconfig/ganesha" is written
> differently on RHEL 7.1. This leads to exports failing all the time on RHEL
> 7.1.
> One of the scripts that ceates the export config file needs modification.

Could you explain a little more details? /etc/sysconfig/ganesha is only(?) used for the parameters for the ganesha.nfsd process. This file is in a simple KEY=VALUE format and is part of the nfs-ganesha RPM. What causes the problem and would need changing? Note that upstream NFS-Ganesha did make some relatively recent changes to this file, not sure if they are in the V2.2-stable branch.
Comment 6 Meghana 2015-07-10 03:12:25 EDT
We grep for CONFFILE parameter in "/etc/syconfig/ganesha"
file to find out the path of the ganesha config file.
In RHEL 7.1, this parameter does not exist in the file and
we can't find out the ganesha config file. Export
fails invariably due to this. Changing this pattern to
a more generic one and default it to "/etc/ganesha/ganesha.conf"
Comment 7 Meghana 2015-07-10 03:13:04 EDT
This patch is up for review in upstream,
http://review.gluster.org/#/c/11594/
Comment 10 Apeksha 2015-07-14 04:17:31 EDT
Able to export ganesha volume on rhel7.1 with the workaround mentioned in:


1. comment 4 of bug -> https://bugzilla.redhat.com/show_bug.cgi?id=1242487#c4
2. comment 2 of bug -> https://bugzilla.redhat.com/show_bug.cgi?id=1241400#c2
Comment 11 errata-xmlrpc 2015-07-29 01:09:17 EDT
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.