Bug 817515

Summary:	object-storage: not required error message about xattr
Product:	[Community] GlusterFS	Reporter:	Saurabh <saujain>
Component:	object-storage	Assignee:	Junaid <junaid>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Saurabh <saujain>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	pre-release	CC:	gluster-bugs, mzywusko, vagarwal
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.4.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-24 17:47:46 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:	3.3.0qa41	Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	817967

Description Saurabh 2012-04-30 11:10:15 UTC

Description of problem:
whenever the parallel PUTs are tried the this error message gets generated frequently,

Apr 30 00:31:38 gqas014 object-server STDOUT: ERROR:root:removexattr failed on /mnt/gluster-object/AUTH_test err: [Errno 61] No data available#012Traceback (most recent call last):#012  File "/usr/lib/python2.6/site-packages/swift/plugins/utils.py", line 316, in check_user_xattr#012    removexattr(path, 'user.test.key1')#012IOError: [Errno 61] No data available (txn: tx975c8dd2a8b1414c95eb7ad09ae06653)

which I assume is unnecessary, as this kind of check is not required during PUT. 

This message is seen even for new container and a container from where all the objects have been removed using "rm-rf" 

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

3.3.0qa38 and gluster-plugin-1.0

How reproducible:
always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Junaid 2012-05-18 01:33:55 UTC

Fixed in latest rpms (rc1).

Comment 2 Saurabh 2012-05-22 07:35:05 UTC

verified on 3.3.0qa41 and latest rpms