Bug 1702298 - Custom xattrs are not healed on newly added brick
Summary: Custom xattrs are not healed on newly added brick
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: distribute
Version: rhgs-3.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: RHGS 3.5.0
Assignee: Mohit Agrawal
QA Contact: Sayalee
URL:
Whiteboard:
Depends On:
Blocks: 1696807 1702299 1753561
TreeView+ depends on / blocked
 
Reported: 2019-04-23 12:40 UTC by Mohit Agrawal
Modified: 2019-10-30 12:21 UTC (History)
4 users (show)

Fixed In Version: glusterfs-6.0-4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1702299 (view as bug list)
Environment:
Last Closed: 2019-10-30 12:20:51 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:3249 0 None None None 2019-10-30 12:21:19 UTC

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


Note You need to log in before you can comment on or make changes to this bug.