Bug 1224165

Summary:	SIGNING FAILURE Error messages are poping up in the bitd log
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	RajeshReddy <rmekala>
Component:	bitrot	Assignee:	Venky Shankar <vshankar>
Status:	CLOSED ERRATA	QA Contact:	RajeshReddy <rmekala>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	rhgs-3.1	CC:	annair, asrivast, bugs, mzywusko, nsathyan, rhs-bugs, rmekala, storage-qa-internal, vagarwal, vshankar
Target Milestone:	---
Target Release:	RHGS 3.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.0-3	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1221938	Environment:
Last Closed:	2015-07-29 04:48:27 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:	1202842

Description RajeshReddy 2015-05-22 09:41:22 UTC

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

Description of problem:
========================
SIGNING FAILURE  Error messages  are poping up in the bitd log

Version-Release number of selected component (if applicable):
==================================
glusterfs-server-3.7.0-2.el6rhs.x86_64

How reproducible:


Steps to Reproduce:
1.Create disribute volume with bricks from two nodes
2.Create direcotry and do some IO and observe the bitd log and able to see follwoing messages 

2015-05-15 05:21:13.362936] W [client-rpc-fops.c:1871:client3_3_fsetxattr_cbk] 0-vol2-client-1: remote operation failed: Invalid argument
[2015-05-15 05:21:13.363083] E [bit-rot.c:446:br_object_read_sign] 0-vol2-bit-rot-0: fsetxattr of signature to the object e2b130b3-8d40-491a-910f-9313effa0157 failed
[2015-05-15 05:21:13.363159] E [bit-rot.c:641:br_sign_object] 0-vol2-bit-rot-0: reading and signing of the object e2b130b3-8d40-491a-910f-9313effa0157 failed
[2015-05-15 05:21:13.363268] E [bit-rot.c:697:br_process_object] 0-vol2-bit-rot-0: SIGNING FAILURE [e2b130b3-8d40-491a-910f-9313effa0157]
[2015-05-15 05:22:35.450467] W [client-rpc-fops.c:1871:client3_3_fsetxattr_cbk] 0-vol2-client-1: remote operation failed: Invalid argument
[2015-05-15 05:22:35.450589] E [bit-rot.c:446:br_object_read_sign] 0-vol2-bit-rot-0: fsetxattr of signature to the object e2b130b3-8d40-491a-910f-9313effa0157 failed
[2015-05-15 05:22:35.450663] E [bit-rot.c:641:br_sign_object] 0-vol2-bit-rot-0: reading and signing of the object e2b130b3-8d40-491a-910f-9313effa0157 failed
[2015-05-15 05:22:35.450803] E [bit-rot.c:697:br_process_object] 0-vol2-bit-rot-0: SIGNING FAILURE [e2b130b3-8d40-491a-910f-9313effa0157]
[2015-05-15 05:23:57.539250] W [client-rpc-fops.c:1871:client3_3_fsetxattr_cbk] 0-vol2-client-1: remote operation failed: Invalid argument
[2015-05-15 05:23:57.539385] E [bit-rot.c:446:br_object_read_sign] 0-vol2-bit-rot-0: fsetxattr of signature to the object e2b130b3-8d40-491a-910f-9313effa0157 failed
[2015-05-15 05:23:57.539455] E [bit-rot.c:641:br_sign_object] 0-vol2-bit-rot-0: reading and signing of the object e2b130b3-8d40-491a-910f-9313effa0157 failed
[2015-05-15 05:23:57.539595] E [bit-rot.c:697:br_process_object] 0-vol2-bit-rot-0: SIGNING FAILURE [e2b130b3-8d40-491a-910f-9313effa0157]


Actual results:


Expected results:


Additional info:

--- Additional comment from Venky Shankar on 2015-05-18 06:09:54 EDT ---

Were there any unlinks/rmdirs in the file tree?

--- Additional comment from Venky Shankar on 2015-05-18 06:17:03 EDT ---

and please check (and paste/upload) brick logs.

--- Additional comment from RajeshReddy on 2015-05-18 07:39:15 EDT ---

There were no unlinks/rmdirs and attaching the brick logs

--- Additional comment from Anand Avati on 2015-05-19 12:07:08 EDT ---

REVIEW: http://review.gluster.org/10832 (features/bitrot: serialize versioning) posted (#1) for review on master by Venky Shankar (vshankar)

Comment 2 RajeshReddy 2015-06-08 07:19:49 UTC

Tested with glusterfs-server-3.7.0-3 build and not able to see failure messages in the bitd log so marking this bug as verified

Comment 3 errata-xmlrpc 2015-07-29 04:48:27 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-1495.html