Bug 1584517 - Inconsistent access permissions on directories after bringing back the down sub-volumes
Summary: Inconsistent access permissions on directories after bringing back the down s...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: distribute
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Mohit Agrawal
QA Contact:
URL:
Whiteboard:
Depends On: 1582066
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-31 06:56 UTC by Mohit Agrawal
Modified: 2018-10-23 15:10 UTC (History)
6 users (show)

Fixed In Version: glusterfs-5.0
Clone Of: 1582066
Environment:
Last Closed: 2018-10-23 15:10:44 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Worker Ant 2018-05-31 07:06:44 UTC
REVIEW: https://review.gluster.org/20107 (dht: Inconsistent permission for directories after brick stop/start) posted (#1) for review on master by MOHIT AGRAWAL

Comment 2 Worker Ant 2018-05-31 07:16:40 UTC
REVIEW: https://review.gluster.org/20108 (dht: Inconsistent permission for directories after brick stop/start) posted (#1) for review on master by MOHIT AGRAWAL

Comment 3 Worker Ant 2018-07-11 03:13:54 UTC
COMMIT: https://review.gluster.org/20108 committed in master by "Amar Tumballi" <amarts> with a commit message- dht: Inconsistent permission for directories after brick stop/start

Problem: Inconsistent access permissions on directories after
         bringing back the down sub-volumes, in case of directories dht_setattr
         first wind a call on MDS once call is finished on MDS then wind a call
         on NON-MDS.At the time of revalidating dht just compare the uid/gid with
         stbuf uid/gid and if anyone differs set a flag to heal the same.

Solution: Add a condition to compare permission also in dht_revalidate_cbk
          to set a flag to call dht_dir_attr_heal.

BUG: 1584517
Change-Id: I3e039607148005015b5d93364536158380d4c5aa
fixes: bz#1584517
Signed-off-by: Mohit Agrawal <moagrawa>

Comment 4 Shyamsundar 2018-10-23 15:10:44 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/


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