Description of problem: Regression test fails for namespace, when brick multiplexing is enabled. How reproducible: Always with brick multiplex enabled. Steps to Reproduce: 1. Run namespace test with brick multiplex enabled Actual results: 09:33:47 ./tests/basic/namespace.t (Wstat: 0 Tests: 33 Failed: 8) 09:33:47 Failed tests: 15-16, 18-19, 21-22, 32-33 09:33:47 Files=1, Tests=33, 94 wallclock secs ( 0.07 usr 0.01 sys + 5.89 cusr 4.36 csys = 10.33 CPU) 09:33:47 Result: FAIL 09:33:47 End of test ./tests/basic/namespace.t Expected results: The namespace test should not have failed.
REVIEW: https://review.gluster.org/19685 (tests/basic/namespace: Fix the namespace test failure) posted (#3) for review on master by Varsha Rao
COMMIT: https://review.gluster.org/19685 committed in master by "Varsha Rao" <varao> with a commit message- tests/basic/namespace: Fix the namespace test failure In the jenkins regression test brick multiplexing is enabled by is_brick_mx_enabled function and not by setting cluster.brick-multiplex option. Hence check the count of bricks and its logs, this fixes the failure. Change-Id: Ibb2ed8fbffd3765f283da741689304a5579d447c BUG: 1555167 Signed-off-by: Varsha Rao <varao>
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-v4.1.0, please open a new bug report. glusterfs-v4.1.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-June/000102.html [2] https://www.gluster.org/pipermail/gluster-users/