Bug 1127148

Summary:	Regression test failure while running bug-918437-sh-mtime.t
Product:	[Community] GlusterFS	Reporter:	Jiffin <jthottan>
Component:	replicate	Assignee:	Ravishankar N <ravishankar>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-bugs, ravishankar
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-05-14 17:27:01 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 Jiffin 2014-08-06 09:28:57 UTC

Description of problem:

./tests/bugs/bug-918437-sh-mtime.t failed on gluster build system with the following error :
stat: cannot stat `/d/backends/gfs0/brick02/b': No such file or directory
[11:16:05] ./tests/bugs/bug-918437-sh-mtime.t ................

It seems that file being checked after performing self heal is wrong.

Test Summary Report
-------------------
./tests/bugs/bug-918437-sh-mtime.t              (Wstat: 0 Tests: 37 Failed: 1)
  Failed test:  37
Files=271, Tests=7911, 4619 wallclock secs ( 2.95 usr  1.75 sys + 426.03 cusr 593.78 csys = 1024.51 CPU)
Result: FAIL
+ RET=1
++ ls -l '/core.*'
++ wc -l
+ cur_count=0
+ '[' 0 '!=' 0 ']'
+ '[' 1 -ne 0 ']'
+ filename=logs/glusterfs-logs-20140805:10:09:52.tgz
+ tar -czf /archives/logs/glusterfs-logs-20140805:10:09:52.tgz /var/log/glusterfs
tar: Removing leading `/' from member names
+ echo Logs archived in http://slave24.cloud.gluster.org/logs/glusterfs-logs-20140805:10:09:52.tgz
Logs archived in http://slave24.cloud.gluster.org/logs/glusterfs-logs-20140805:10:09:52.tgz
+ exit 1
+ RET=1
+ '[' 1 = 0 ']'
+ V=-1
+ VERDICT=FAILED
+ ssh build.org gerrit review --message ''\''http://build.gluster.org/job/rackspace-regression-2GB-triggered/688/consoleFull : FAILED'\''' --project=glusterfs --verified=-1 --code-review=0 843c006d2ba4a58fa04ba1e040467f9d06954ced
+ exit 1
Build step 'Execute shell' marked build as failure
Finished: FAILURE

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


How reproducible:
Regression test by gluster bulid system

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Anand Avati 2014-08-13 05:02:31 UTC

REVIEW: http://review.gluster.org/8465 (tests: trigger entry heals by lookup) posted (#1) for review on master by Ravishankar N (ravishankar)

Comment 2 Anand Avati 2014-08-13 09:53:07 UTC

COMMIT: http://review.gluster.org/8465 committed in master by Pranith Kumar Karampuri (pkarampu) 
------
commit 250210a36bfd5b5c44ad49ca1c3f6aef148da322
Author: Ravishankar N <ravishankar>
Date:   Wed Aug 13 10:17:50 2014 +0530

    tests: trigger entry heals by lookup
    
    Trigger entry heals explicitly by lookup until heal full is fixed in
    afr v2 to do conservative merge.
    
    Change-Id: I474b518045bebcf399bc414caff3b415259381d6
    BUG: 1127148
    Signed-off-by: Ravishankar N <ravishankar>
    Reviewed-on: http://review.gluster.org/8465
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    Tested-by: Pranith Kumar Karampuri <pkarampu>

Comment 3 Niels de Vos 2015-05-14 17:27:01 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:31 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:37:53 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:43:05 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