Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1615239

Summary:	Fix ./tests/basic/afr/replace-brick-self-heal.t failure
Product:	[Community] GlusterFS	Reporter:	Ravishankar N <ravishankar>
Component:	tests	Assignee:	Ravishankar N <ravishankar>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-5.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-23 15:17:10 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 Ravishankar N 2018-08-13 06:31:45 UTC

Description of problem:

https://build.gluster.org/job/line-coverage/471/consoleFull
---------------------------------------------------------------------------------
./tests/basic/afr/replace-brick-self-heal.t
04:28:44   Failed tests:  22, 26, 28

04:28:44 not ok 22 Got "5" instead of "0", LINENUM:46

04:28:44 not ok 26 , LINENUM:56
04:28:44 FAILED COMMAND: diff /d/backends/patchy0/file1.txt /d/backends/patchy1_new/file1.txt

04:28:44 not ok 28 Got "" instead of "qwerty", LINENUM:61
04:28:44 FAILED COMMAND: qwerty get_text_xattr user.test /d/backends/patchy1_new/file5.txt
--------------------------------------------------------------------------------

From shd log, it is seen that data-selfheal has not yet started but heal time-out was hit:

[2018-08-12 04:27:27.250366]:++++++++++ G_LOG:./tests/basic/afr/replace-brick-self-heal.t: TEST: 40 Y glustershd_up_status ++++++++++
[2018-08-12 04:27:27.376354]:++++++++++ G_LOG:./tests/basic/afr/replace-brick-self-heal.t: TEST: 41 1 afr_child_up_status_in_shd patchy 0 ++++++++++
[2018-08-12 04:27:28.457533]:++++++++++ G_LOG:./tests/basic/afr/replace-brick-self-heal.t: TEST: 42 1 afr_child_up_status_in_shd patchy 1 ++++++++++
[2018-08-12 04:27:29.521107]:++++++++++ G_LOG:./tests/basic/afr/replace-brick-self-heal.t: TEST: 43 gluster --mode=script --wignore volume heal patchy ++++++++++
[2018-08-12 04:27:29.607822] I [MSGID: 108026] [afr-self-heal-metadata.c:52:__afr_selfheal_metadata_do] 0-patchy-replicate-0: performing metadata selfheal on 00000000-0000-0000-0000-000000000001
<snipped>
[2018-08-12 04:27:29.622833] I [MSGID: 108026] [afr-self-heal-common.c:1730:afr_log_selfheal] 0-patchy-replicate-0: Completed metadata selfheal on 00000000-0000-0000-0000-000000000001. sources=[0]  sinks=1
[2018-08-12 04:27:29.627898] I [MSGID: 108026] [afr-self-heal-entry.c:887:afr_selfheal_entry_do] 0-patchy-replicate-0: performing entry selfheal on 00000000-0000-0000-0000-000000000001
[2018-08-12 04:27:29.629383]:++++++++++ G_LOG:./tests/basic/afr/replace-brick-self-heal.t: TEST: 46 0 get_pending_heal_count patchy ++++++++++
<snipped>
[2018-08-12 04:27:29.675832] I [MSGID: 108026] [afr-self-heal-common.c:1730:afr_log_selfheal] 0-patchy-replicate-0: Completed entry selfheal on 00000000-0000-0000-0000-000000000001. sources= sinks=0 1
[2018-08-12 04:28:49.163183]:++++++++++ G_LOG:./tests/basic/afr/replace-brick-self-heal.t: TEST: 49 diff /dev/fd/63 /dev/fd/62 ++++++++++
--------------------------------------------------------------------------------

This looks identical to BZ 1613807

Comment 1 Worker Ant 2018-08-13 06:48:22 UTC

REVIEW: https://review.gluster.org/20717 (tests: fix replace-brick-self-heal.t failure) posted (#1) for review on master by Ravishankar N

Comment 2 Worker Ant 2018-08-13 12:10:46 UTC

COMMIT: https://review.gluster.org/20717 committed in master by "Shyamsundar Ranganathan" <srangana> with a commit message- tests: fix replace-brick-self-heal.t failure

Please see BZ for details.

Change-Id: Id9273432874bc6a452ac96b2b8c7a61ea6c5b98d
Fixes: bz#1615239
Signed-off-by: Ravishankar N <ravishankar>

Comment 3 Shyamsundar 2018-10-23 15:17:10 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-5.0, please open a new bug report.

glusterfs-5.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] https://lists.gluster.org/pipermail/announce/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/