Bug 1472094 - Test script failing with brick multiplexing enabled
Summary: Test script failing with brick multiplexing enabled
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: disperse
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Sunil Kumar Acharya
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1472794
TreeView+ depends on / blocked
 
Reported: 2017-07-18 05:34 UTC by Sunil Kumar Acharya
Modified: 2017-09-05 17:37 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.12.0
Clone Of:
: 1472794 (view as bug list)
Environment:
Last Closed: 2017-08-21 08:21:54 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Sunil Kumar Acharya 2017-07-18 05:34:10 UTC
Update the test script to avoid failures with brick multiplexing enabled.

Comment 1 Worker Ant 2017-07-18 06:10:52 UTC
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)

Comment 2 Worker Ant 2017-07-18 11:51:19 UTC
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 3 Shyamsundar 2017-09-05 17:37:29 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.12.0, please open a new bug report.

glusterfs-3.12.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/2017-September/000082.html
[2] https://www.gluster.org/pipermail/gluster-users/


Note You need to log in before you can comment on or make changes to this bug.