Bug 1702298

Summary: Custom xattrs are not healed on newly added brick
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Mohit Agrawal <moagrawa>
Component: distributeAssignee: Mohit Agrawal <moagrawa>
Status: CLOSED ERRATA QA Contact: Sayalee <saraut>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.5CC: rhinduja, rhs-bugs, sheggodu, storage-qa-internal
Target Milestone: ---   
Target Release: RHGS 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-6.0-4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1702299 (view as bug list) Environment:
Last Closed: 2019-10-30 12:20:51 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: 1696807, 1702299, 1753561    

Description Mohit Agrawal 2019-04-23 12:40:15 UTC
Description of problem:
Custom xattrs are not healed on newly added brick

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


How reproducible:
Always

Steps to Reproduce:
1.Setup 1x4 volume and mount the volume on /mnt
2.Create some directory mkdir /mnt/tmp{1..10}
3.Setup user.foo on all directories
  setfattr -n user.foo -v "abc" /mnt/tmp{1..10}
4. Added two new bricks
5. Run lookup on mount point
   ls -laR /mnt/    
6. Check xattr should heal for all directories on the backend on 
   newly added bricks
   
Actual results:

xattr are not healed on newly added brick
Expected results:
xattr should heal on newly added brick

Additional info:

Comment 9 errata-xmlrpc 2019-10-30 12:20:51 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://access.redhat.com/errata/RHEA-2019:3249