Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1658733

Summary:	tests/bugs/glusterd/rebalance-operations-in-single-node.t is failing in brick mux regression
Product:	[Community] GlusterFS	Reporter:	Sanju <srakonde>
Component:	glusterd	Assignee:	Sanju <srakonde>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.12	CC:	amukherj, atumball, bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-09 05:36:26 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:

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.