Bug 1469988

Summary:	nfs-ganesha: Revert fixes needed to run NFS-Ganesha in RHGS as non-root user
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Soumya Koduri <skoduri>
Component:	nfs-ganesha	Assignee:	Soumya Koduri <skoduri>
Status:	CLOSED ERRATA	QA Contact:	Manisha Saini <msaini>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.3	CC:	amukherj, asoman, ffilz, msaini, rcyriac, rhinduja, rhs-bugs, storage-qa-internal
Target Milestone:	---
Target Release:	RHGS 3.3.0
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	nfs-ganesha-2.4.4-15	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-09-21 04:47:57 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:	1417151

Description Soumya Koduri 2017-07-12 08:33:18 UTC

Description of problem:

There were few fixes needed to be able to run NFS-Ganesha as non-root user (for bug1450836). 
Changes which went in to 
* nfs-ganesha build are as part of bug1450836 & bug1465536 
* glusterfs codebase - 1459972


But since the changes in nfs-ganesha codebase have caused regressions, it was decided to drop this feature support in RHGS 3.3.0 for now and to be added in future.

This bug is to revert those changes from RHGS 3.3.0 nfs-ganesha code base (i.e, bug1450836 & bug1465536 fixes)

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 Manisha Saini 2017-07-14 17:30:28 UTC

AS the build is available to QE which do not have non-root user fixes,Hence moving this bug to verified state.

# rpm -qa | grep ganesha
nfs-ganesha-2.4.4-15.el7rhgs.x86_64
nfs-ganesha-gluster-2.4.4-15.el7rhgs.x86_64
glusterfs-ganesha-3.8.4-33.el7rhgs.x86_64

Comment 6 errata-xmlrpc 2017-09-21 04:47:57 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://access.redhat.com/errata/RHEA-2017:2779