Bug 1213066

Summary: Failure in tests/performance/open-behind.t
Product: [Community] GlusterFS Reporter: Vijay Bellur <vbellur>
Component: open-behindAssignee: Vijay Bellur <vbellur>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs, rtalur
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.8rc2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1217879 (view as bug list) Environment:
Last Closed: 2016-06-16 12:52:58 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: 1217879    

Description Vijay Bellur 2015-04-18 13:24:26 UTC
Description of problem:

The following test fails at random in regression test runs.

    tests/performance/open-behind.t  
      Happens in master - Failed test:  17

Root cause points to time involved in performing a graph switch on the client.


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-04-18 13:27:06 UTC
REVIEW: http://review.gluster.org/10293 (tests: Await for graph switch before testing open fop count) posted (#1) for review on master by Vijay Bellur (vbellur)

Comment 2 Anand Avati 2015-04-19 05:36:12 UTC
REVIEW: http://review.gluster.org/10293 (tests: Await for graph switch before testing open fop count) posted (#2) for review on master by Vijay Bellur (vbellur)

Comment 3 Anand Avati 2015-04-29 14:03:13 UTC
COMMIT: http://review.gluster.org/10293 committed in master by Raghavendra Bhat (raghavendra) 
------
commit 797e923da9f5f1eca4a51da177b1a7cbef75b5ad
Author: Vijay Bellur <vbellur>
Date:   Sat Apr 18 18:40:55 2015 +0530

    tests: Await for graph switch before testing open fop count
    
    In performance/open-behind.t, a test for open fop reaching the brick is done by
    switching off open-behind and performing a read operation. If the read operation
    is performed before a graph switch, the read happens on the old graph and hence
    open does not get accounted in the brick.
    
    To overcome this EXPECT_WITHIN 10 seconds has now been added to ensure that a
    graph switch has happened. The read operation happens subsequently after the
    graph switch.
    
    Cleaned up a "No volumes present" message from stderr while doing this.
    
    Change-Id: I1e1c0d7e4bd2057520b4dd46157d18f30837b8c9
    BUG: 1213066
    Signed-off-by: Vijay Bellur <vbellur>
    Reviewed-on: http://review.gluster.org/10293
    Reviewed-by: Krishnan Parthasarathi <kparthas>
    Reviewed-by: Raghavendra Bhat <raghavendra>
    Tested-by: Raghavendra Bhat <raghavendra>

Comment 4 Raghavendra Talur 2016-03-10 07:25:47 UTC
This test is now fixed. Moved it to open-behind component.

"tests" component is for tests framework only.
File a bug under test component if you find a bug in 
1. any of the *.rc files under tests/ 
2. run-tests.sh


For everything else, the bug should be filed on
1. component which is being tested by .t file if the .t file requires fix.
2. component which is causing a valid .t file to fail in regression.

I have used my best judgement here to move the bug to right component.
In case of ambiguity, I have placed the blame on the .t file component.

Please consider test bugs under the same backlog list that tracks other bugs in your component.

Comment 5 Niels de Vos 2016-06-16 12:52:58 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