Bug 1645986 - tests/bugs/glusterd/optimized-basic-testcases-in-cluster.t failing in distributed regression
Summary: tests/bugs/glusterd/optimized-basic-testcases-in-cluster.t failing in distrib...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Sanju
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-05 06:21 UTC by Sanju
Modified: 2020-01-09 17:30 UTC (History)
1 user (show)

Fixed In Version: glusterfs-6.0
Clone Of:
Environment:
Last Closed: 2019-03-25 16:31:44 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 21545 0 None Merged glusterd: initialise caps inside #ifdef HAVE_BD_XLATOR block 2018-11-06 06:03:11 UTC

Description Sanju 2018-11-05 06:21:18 UTC
Description of problem:
tests/bugs/glusterd/optimized-basic-testcases-in-cluster.t failing in distributed regression, when we run this test case with bd xlator disabled.

Version-Release number of selected component (if applicable):
mainline

How reproducible:
Always

Steps to Reproduce:
1. disable bd xlator while ./configure
2. run tests/bugs/glusterd/optimized-basic-testcases-in-cluster.t
3. 

Actual results:
test case will fail

Expected results:
test case should succeed

Additional info:

Comment 1 Worker Ant 2018-11-05 06:24:20 UTC
REVIEW: https://review.gluster.org/21545 (glusterd: initialise caps inside #ifdef HAVE_BD_XLATOR block) posted (#1) for review on master by Sanju Rakonde

Comment 2 Worker Ant 2018-11-06 06:03:10 UTC
REVIEW: https://review.gluster.org/21545 (glusterd: initialise caps inside #ifdef HAVE_BD_XLATOR block) posted (#2) for review on master by Atin Mukherjee

Comment 3 Shyamsundar 2019-03-25 16:31:44 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-6.0, please open a new bug report.

glusterfs-6.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] https://lists.gluster.org/pipermail/announce/2019-March/000120.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.