Bug 1658733 - tests/bugs/glusterd/rebalance-operations-in-single-node.t is failing in brick mux regression
Summary: tests/bugs/glusterd/rebalance-operations-in-single-node.t is failing in brick...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.12
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Sanju
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-12 18:32 UTC by Sanju
Modified: 2020-01-09 17:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-09 05:36:26 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 21850 0 None Abandoned tests: use $REBALANCE_TIMEOUT variable instead of a random number 2019-03-07 07:08:46 UTC

Description Sanju 2018-12-12 18:32:36 UTC
Description of problem:
tests/bugs/glusterd/rebalance-operations-in-single-node.t failed in brick-mux regression.

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

Additional info:
Logs can be found at https://build.gluster.org/job/regression-on-demand-multiplex/447/consoleFull

Comment 1 Worker Ant 2018-12-12 18:35:55 UTC
REVIEW: https://review.gluster.org/21850 (glusterd: use $REBALANCE_TIMEOUT variable instead of a random number) posted (#1) for review on master by Sanju Rakonde

Comment 2 Sanju 2018-12-12 18:39:13 UTC
The test case was also failing at "EXPECT_WITHIN 90 "completed" rebalance_status_field $V0" (line #122). The above patch fixes this problem, however the issue reported in brick-mux regression is yet to be root caused.

Comment 3 Amar Tumballi 2019-05-18 06:34:56 UTC
I don't see this test failing regression anymore. Did we fix this?

Comment 4 Sanju 2019-05-18 06:38:41 UTC
As per my knowledge, we didn't fix it yet. It might be got fixed by some change, that is why we are not seeing this failure in recent brick-mux regressions.

Thanks,
Sanju

Comment 5 Atin Mukherjee 2019-06-09 05:36:26 UTC
I do not see a reason in keeping this bug open given we don't see this test failing any longer in recent regressions.


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