Bug 1219028

Summary:	Spurious regression failures in uss.t
Product:	[Community] GlusterFS	Reporter:	Jeff Darcy <jdarcy>
Component:	snapshot	Assignee:	Jeff Darcy <jdarcy>
Status:	CLOSED EOL	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.7.0	CC:	bugs, rtalur
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1209286	Environment:
Last Closed:	2017-03-08 11:03: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:	1209286, 1218576
Bug Blocks:	1225077

Description Jeff Darcy 2015-05-06 12:40:36 UTC

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

The failing test is #26 (line 78), which tries to list .snaps immediately after a mount.

--- Additional comment from Anand Avati on 2015-04-06 20:46:13 EDT ---

REVIEW: http://review.gluster.org/10143 (tests: fix spurious regression in uss.t) posted (#1) for review on master by Jeff Darcy (jdarcy)

--- Additional comment from Anand Avati on 2015-04-07 01:37:41 EDT ---

COMMIT: http://review.gluster.org/10143 committed in master by Vijay Bellur (vbellur) 
------
commit 2ef9ad2dc5822b9b88243cb7f60816fe1c531e91
Author: Jeff Darcy <jdarcy>
Date:   Mon Apr 6 20:44:09 2015 -0400

    tests: fix spurious regression in uss.t
    
    Sometimes .snaps just doesn't seem to be available right after a
    mount.  I have no idea, but maybe wrapping the next command in an
    EXPECT_WITHIN will cut down on the spurious test failures.
    
    Change-Id: I9bfda9d34e10ff0b783337e700ab8255dc6795ab
    BUG: 1209286
    Signed-off-by: Jeff Darcy <jdarcy>
    Reviewed-on: http://review.gluster.org/10143
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 1 Raghavendra Talur 2016-03-08 19:49:59 UTC

"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 2 Kaushal 2017-03-08 11:03:38 UTC

This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.