Bug 1456341

Summary:	nfs-ganesha: Rebuild with latest libntirpc available [RHEL7]
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.2	CC:	bmohanra, msaini, rcyriac, rhinduja, rhs-bugs, storage-qa-internal
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.2.0 Async
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	nfs-ganesha-2.4.1-10	Doc Type:	Bug Fix
Doc Text:	An updated version of libntirpc (1.4.3-4) that contains changes to the transport-independent RPC (TI-RPC) library for NFS-Ganesha is included in this package. Since, NFS-Ganesha consumes those functions, it is now recompiled against libntirpc-1.4.3.4.	Story Points:	---
Clone Of:
Clones:	1456342 1456660 (view as bug list)		Environment:
Last Closed:	2017-06-13 10:08: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:	1456342, 1456660

Description Soumya Koduri 2017-05-29 07:29:00 UTC

Description of problem:

With bug1448862, we have new version of ntirpc library available which have changes to inline macros. This would need rebuild of nfs-ganesha package as well.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 5 Manisha Saini 2017-06-12 17:43:12 UTC

Verified this with

# rpm -qa | grep ganesha
nfs-ganesha-2.4.1-10.el7rhgs.x86_64
glusterfs-ganesha-3.8.4-18.4.el7rhgs.x86_64
nfs-ganesha-gluster-2.4.1-10.el7rhgs.x86_64

# rpm -qa | grep libnt
libntirpc-1.4.3-4.el7rhgs.x86_64

Hence moving this bug to verified state.

Comment 7 errata-xmlrpc 2017-06-13 10:08: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://access.redhat.com/errata/RHBA-2017:1433