Bug 1217788

Summary:	spurious failure bug-908146.t
Product:	[Community] GlusterFS	Reporter:	Pranith Kumar K <pkarampu>
Component:	tests	Assignee:	Pranith Kumar K <pkarampu>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	amukherj, bugs, gluster-bugs
Target Milestone:	---	Keywords:	Reopened, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1218485 (view as bug list)		Environment:
Last Closed:	2016-06-16 12:57:38 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:
Bug Depends On:
Bug Blocks:	1218485

Description Pranith Kumar K 2015-05-01 16:24:02 UTC

Description of problem:
Flush behind is on by default so closing the file on mount may not result in close on the brick synchronously.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Anand Avati 2015-05-01 16:24:28 UTC

REVIEW: http://review.gluster.org/10488 (tests: Disable flush behind so that file will be closed) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)

Comment 2 Anand Avati 2015-05-03 11:22:05 UTC

COMMIT: http://review.gluster.org/10488 committed in master by Pranith Kumar Karampuri (pkarampu) 
------
commit deedac1101c109895c9aff8e7a1171bea16a6d5e
Author: Pranith Kumar K <pkarampu>
Date:   Fri May 1 21:51:09 2015 +0530

    tests: Disable flush behind so that file will be closed
    
    Change-Id: I97eb8d236448e8783f09b4922aa465a2b1b3979b
    BUG: 1217788
    Signed-off-by: Pranith Kumar K <pkarampu>
    Reviewed-on: http://review.gluster.org/10488
    Tested-by: Gluster Build System <jenkins.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Niels de Vos <ndevos>
    Reviewed-by: Krutika Dhananjay <kdhananj>

Comment 3 Nagaprasad Sathyanarayana 2015-10-25 14:53:36 UTC

Fix for this bug is already made in a GlusterFS release. The cloned BZ has details of the fix and the release. Hence closing this mainline BZ.

Comment 4 Nagaprasad Sathyanarayana 2015-10-25 14:54:17 UTC

Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.

Comment 5 Niels de Vos 2016-06-16 12:57:38 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-3.8.0, please open a new bug report.

glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user