Bug 1521030

Summary:	rpc: unregister programs before registering them again
Product:	[Community] GlusterFS	Reporter:	Amar Tumballi <atumball>
Component:	rpc	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-v4.1.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-20 17:57:42 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:

Description Amar Tumballi 2017-12-05 16:30:54 UTC

Description of problem:
Noticed that there is possibility of duplicate program registration in the flow of init() (reconnects etc). Should be taking care to unregister programs before registering.

Comment 1 Worker Ant 2017-12-05 16:32:41 UTC

REVIEW: https://review.gluster.org/18926 (rpc: update tirpc registration to \"force\" unregister old mapping before re-registering) posted (#1) for review on master by Amar Tumballi

Comment 2 Worker Ant 2018-03-28 03:14:07 UTC

REVIEW: https://review.gluster.org/18926 (rpc: update tirpc registration to \"force\" unregister old mapping before re-registering) posted (#4) for review on master by Amar Tumballi

Comment 3 Worker Ant 2018-03-28 07:39:32 UTC

COMMIT: https://review.gluster.org/18926 committed in master by "Amar Tumballi" <amarts> with a commit message- rpc: update tirpc registration to "force" unregister old mapping before re-registering

> Reviewed-on: https://review.gluster.org/16849
> Reviewed-by: Shreyas Siravara <sshreyas>

Change-Id: I05ed6b7c715a71e5819fbe8116e7c3146010f836
BUG: 1521030
Signed-off-by: Kevin Vigor <kvigor>
Signed-off-by: Amar Tumballi <amarts>

Comment 4 Shyamsundar 2018-06-20 17:57:42 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-v4.1.0, please open a new bug report.

glusterfs-v4.1.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2018-June/000102.html
[2] https://www.gluster.org/pipermail/gluster-users/