Bug 1472794

Summary:	Test script failing with brick multiplexing enabled
Product:	[Community] GlusterFS	Reporter:	Sunil Kumar Acharya <sheggodu>
Component:	disperse	Assignee:	Sunil Kumar Acharya <sheggodu>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.11	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.11.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1472094	Environment:
Last Closed:	2017-08-12 13:08:02 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:	1472094
Bug Blocks:

Description Sunil Kumar Acharya 2017-07-19 12:14:50 UTC

+++ This bug was initially created as a clone of Bug #1472094 +++

Update the test script to avoid failures with brick multiplexing enabled.

--- Additional comment from Worker Ant on 2017-07-18 02:10:52 EDT ---

REVIEW: https://review.gluster.org/17809 (cluster/ec: Test script failing with brick multiplexing enabled) posted (#1) for review on master by Sunil Kumar Acharya (sheggodu)

--- Additional comment from Worker Ant on 2017-07-18 07:51:19 EDT ---

COMMIT: https://review.gluster.org/17809 committed in master by Pranith Kumar Karampuri (pkarampu) 
------
commit ae14513eb82929662b11e4c304877030a7d685cd
Author: Sunil Kumar Acharya <sheggodu>
Date:   Tue Jul 18 11:36:19 2017 +0530

    cluster/ec: Test script failing with brick multiplexing enabled
    
    Problem:
    Killing the bricks(using kill signal) in test scripts will
    result in test failures with brick multiplexing enabled.
    
    Solution:
    Updated the script to use kill_brick function to bring down
    the bricks.
    
    BUG: 1472094
    Change-Id: Ibbf1fdc1be660ad3cd93e95af2838c0aae0181af
    Signed-off-by: Sunil Kumar Acharya <sheggodu>
    Reviewed-on: https://review.gluster.org/17809
    Smoke: Gluster Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>

Comment 1 Worker Ant 2017-07-19 12:26:04 UTC

REVIEW: https://review.gluster.org/17823 (cluster/ec: Test script failing with brick multiplexing enabled) posted (#1) for review on release-3.11 by Sunil Kumar Acharya (sheggodu)

Comment 2 Worker Ant 2017-07-20 11:51:59 UTC

COMMIT: https://review.gluster.org/17823 committed in release-3.11 by Shyamsundar Ranganathan (srangana) 
------
commit a8d93a1498458a121f8670504dcb639635566347
Author: Sunil Kumar Acharya <sheggodu>
Date:   Tue Jul 18 11:36:19 2017 +0530

    cluster/ec: Test script failing with brick multiplexing enabled
    
    Problem:
    Killing the bricks(using kill signal) in test scripts will
    result in test failures with brick multiplexing enabled.
    
    Solution:
    Updated the script to use kill_brick function to bring down
    the bricks.
    
    >BUG: 1472094
    >Change-Id: Ibbf1fdc1be660ad3cd93e95af2838c0aae0181af
    >Signed-off-by: Sunil Kumar Acharya <sheggodu>
    >Reviewed-on: https://review.gluster.org/17809
    >Smoke: Gluster Build System <jenkins.org>
    >CentOS-regression: Gluster Build System <jenkins.org>
    >Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    
    BUG: 1472794
    Change-Id: Ibbf1fdc1be660ad3cd93e95af2838c0aae0181af
    Signed-off-by: Sunil Kumar Acharya <sheggodu>
    Reviewed-on: https://review.gluster.org/17823
    Smoke: Gluster Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana>

Comment 3 Shyamsundar 2017-08-12 13:08:02 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-3.11.2, please open a new bug report.

glusterfs-3.11.2 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/gluster-users/2017-July/031908.html
[2] https://www.gluster.org/pipermail/gluster-users/