Bug 1599250

Summary:	bug-1432542-mpx-restart-crash.t takes a lot of time to complete cleanup
Product:	[Community] GlusterFS	Reporter:	Xavi Hernandez <jahernan>
Component:	tests	Assignee:	Mohit Agrawal <moagrawa>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, moagrawa
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-5.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-23 15:13:48 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 Xavi Hernandez 2018-07-09 10:08:41 UTC

Description of problem:

The script is taking more time than expected (300 seconds) to complete the cleanup of the created volumes.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2018-07-09 10:13:51 UTC

REVIEW: https://review.gluster.org/20482 (bug-1432542-mpx-restart-crash.t: increase SCRIPT_TIMEOUT time) posted (#1) for review on master by Xavi Hernandez

Comment 2 Worker Ant 2018-07-09 11:15:30 UTC

REVIEW: https://review.gluster.org/20480 (core: Increase SCRIPT_TIMEOUT for bug-1432542-mpx-restart-crash.t) posted (#2) for review on master by Amar Tumballi

Comment 3 Worker Ant 2018-07-09 11:29:42 UTC

COMMIT: https://review.gluster.org/20480 committed in master by "MOHIT AGRAWAL" <moagrawa> with a commit message- core: Increase SCRIPT_TIMEOUT for bug-1432542-mpx-restart-crash.t

BUG: 1599250
Change-Id: I27bda2a0764580289e7154766e13a0c358cba3a8
fixes: bz#1599250
Signed-off-by: Mohit Agrawal <moagrawal>

Comment 4 Shyamsundar 2018-10-23 15:13:48 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-5.0, please open a new bug report.

glusterfs-5.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] https://lists.gluster.org/pipermail/announce/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/