Bug 1218485

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:	3.7.0	CC:	amukherj, bugs, gluster-bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1217788	Environment:
Last Closed:	2015-05-14 17:29:36 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:	1217788
Bug Blocks:

Description Pranith Kumar K 2015-05-05 04:55:41 UTC

+++ This bug was initially created as a clone of Bug #1217788 +++

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:

--- Additional comment from Anand Avati on 2015-05-01 12:24:28 EDT ---

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)

--- Additional comment from Anand Avati on 2015-05-03 07:22:05 EDT ---

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 1 Anand Avati 2015-05-06 01:47:10 UTC

REVIEW: http://review.gluster.org/10543 (tests: Fix spurious failures) posted (#2) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)

Comment 2 Anand Avati 2015-05-06 06:02:20 UTC

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

    tests: Fix spurious failures
    
            Backport of: http://review.gluster.org/10480
                         http://review.gluster.org/10487
                         http://review.gluster.org/10488
                         http://review.gluster.com/10540
    
    - Use REBALANCE_TIMEOUT in EXPECT_WITHIN
    - Use fdatasync to prevent write - behind from giving success
    - Add logfile to glupy
    - Check aux umount is unmounted for quota tests
    - Disable flush behind so that file will be closed
    
    Change-Id: Ia2447176273557738b7a71cc25dd9b9effc16d58
    BUG: 1218485
    Signed-off-by: Pranith Kumar K <pkarampu>
    Reviewed-on: http://review.gluster.org/10543
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 3 Niels de Vos 2015-05-14 17:29:36 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 4 Niels de Vos 2015-05-14 17:35:59 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 5 Niels de Vos 2015-05-14 17:38:20 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 6 Niels de Vos 2015-05-14 17:47:12 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user