Bug 1533594 - EC test fails when brick mux is enabled
Summary: EC test fails when brick mux is enabled
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: tests
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-11 17:26 UTC by Sunil Kumar Acharya
Modified: 2018-03-15 11:24 UTC (History)
1 user (show)

Fixed In Version: glusterfs-4.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-15 11:24:53 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Sunil Kumar Acharya 2018-01-11 17:26:46 UTC 
Description of problem:

tests/basic/ec/ec-fix-openfd.t fails when brick mux is enabled.
Comment 1 Worker Ant 2018-01-11 17:58:23 UTC 
REVIEW: https://review.gluster.org/19184 (tests: EC test fails with brick mux enabled) posted (#1) for review on master by Sunil Kumar Acharya
Comment 2 Worker Ant 2018-01-15 09:51:32 UTC 
COMMIT: https://review.gluster.org/19184 committed in master by \"Sunil Kumar Acharya\" <sheggodu> with a commit message- tests: EC test fails with brick mux enabled

Problem:
With brick mux enabled get_fd_count count was returning
wrong value due to parsing issue.

Solution:
Updated the code to fix parsing problem.

BUG: 1533594
Change-Id: I5d7ff6843b4760f866c4a5aab2f13ff7380f248e
Signed-off-by: Sunil Kumar Acharya <sheggodu>
Comment 3 Shyamsundar 2018-03-15 11:24:53 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-4.0.0, please open a new bug report.

glusterfs-4.0.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-March/000092.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.