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
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
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.
I don't see this test failing regression anymore. Did we fix this?
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
I do not see a reason in keeping this bug open given we don't see this test failing any longer in recent regressions.