Bug 1555167

Summary:	namespace test failure
Product:	[Community] GlusterFS	Reporter:	Varsha <varao>
Component:	tests	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	amukherj, bugs, varao
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	All
Whiteboard:
Fixed In Version:	glusterfs-v4.1.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-20 18:02: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 Varsha 2018-03-14 05:08:40 UTC

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.

Comment 1 Worker Ant 2018-03-14 05:25:26 UTC

REVIEW: https://review.gluster.org/19685 (tests/basic/namespace: Fix the namespace test failure) posted (#3) for review on master by Varsha Rao

Comment 2 Worker Ant 2018-03-14 05:55:01 UTC

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>

Comment 3 Shyamsundar 2018-06-20 18:02:26 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-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/