Bug 1570011

Summary:	test case is failing ./tests/bugs/glusterd/add-brick-and-validate-replicated-volume-options.t while brick mux is enabled
Product:	[Community] GlusterFS	Reporter:	Mohit Agrawal <moagrawa>
Component:	glusterd	Assignee:	Sanju <srakonde>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, srakonde
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 18:05:09 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 Mohit Agrawal 2018-04-20 12:44:51 UTC

Description of problem:

Test case is failing ./tests/bugs/glusterd/add-brick-and-validate-replicated-volume-options.t while brick mux is enabled
Version-Release number of selected component (if applicable):


How reproducible:

Always
Steps to Reproduce:
1.Enable brick mux on latest upstream code
2.Run the test case to verify the same
3.

Actual results:
Test case is failing

Expected results:
Test case should not fail

Additional info:

Comment 1 Worker Ant 2018-04-23 10:36:56 UTC

REVIEW: https://review.gluster.org/19924 (glusterfsd: initiate pmap_signout for all detach brick requests) posted (#1) for review on master by Atin Mukherjee

Comment 2 Worker Ant 2018-05-04 04:50:40 UTC

COMMIT: https://review.gluster.org/19924 committed in master by "Amar Tumballi" <amarts> with a commit message- glusterfsd: initiate pmap_signout for all detach brick requests

In glusterfs_handle_terminate all bricks getting detached need to
initiate a pmap_signout.

Change-Id: Iacbd6fcd49215fe6a5210df7dfed1260fde9179a
Fixes: bz#1570011
Signed-off-by: Atin Mukherjee <amukherj>

Comment 3 Shyamsundar 2018-06-20 18:05:09 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/