Bug 1374573 - gluster fails to propagate permissions on the root of a gluster export when adding bricks
Summary: gluster fails to propagate permissions on the root of a gluster export when a...
Alias: None
Product: GlusterFS
Classification: Community
Component: distribute
Version: 3.8
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Susant Kumar Palai
QA Contact:
URL: dht-file-permission triaged
Depends On: 1082671 1294035 1368012
Blocks: 1286204
TreeView+ depends on / blocked
Reported: 2016-09-09 06:13 UTC by Susant Kumar Palai
Modified: 2016-10-20 14:02 UTC (History)
15 users (show)

Fixed In Version: glusterfs-3.8.5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1368012
Last Closed: 2016-10-20 14:02:35 UTC
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:

Attachments (Terms of Use)

Comment 1 Niels de Vos 2016-09-12 05:36:50 UTC
All 3.8.x bugs are now reported against version 3.8 (without .x). For more information, see http://www.gluster.org/pipermail/gluster-devel/2016-September/050859.html

Comment 2 Worker Ant 2016-09-12 07:50:22 UTC
REVIEW: http://review.gluster.org/15465 (cluster/dht: heal root permission post add-brick) posted (#1) for review on release-3.8 by Susant Palai (spalai@redhat.com)

Comment 3 Worker Ant 2016-09-14 06:33:09 UTC
COMMIT: http://review.gluster.org/15465 committed in release-3.8 by Raghavendra G (rgowdapp@redhat.com) 
commit a9ee05a6673486ef86f36a87e00d144cfb56cf9b
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Aug 17 15:10:04 2016 +0530

    cluster/dht: heal root permission post add-brick
    Post add-brick event the new brick will have permission of 755
    by default. If the root directory permission was other than 755,
    that does not get healed to the new brick leading to permission
    For choosing source of attr heal we can trust the subvols which
    have layouts with latest ctime(as part of missing directory heal,
    we heal the proper attr). In case none of the subvols have layout,
    return ESTALE to retrigger a fresh lookup.
    Note: This patch heals the permission of the root directories only.
    Since, permission healing of directory is not straight forward and
    required intrusive fix, those are not addressed here.
    > Reviewed-on: http://review.gluster.org/15195
    > Smoke: Gluster Build System <jenkins@build.gluster.org>
    > CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    > NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    >Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    (cherry picked from commit 801cd07a4c6ec65ff930b2ae6bb5e405ccd03334)
    Change-Id: If894e3895d070d46b62d2452e52c1eaafcf56c29
    BUG: 1374573
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/15465
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

Comment 4 Niels de Vos 2016-10-20 14:02:35 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-3.8.5, please open a new bug report.

glusterfs-3.8.5 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://www.gluster.org/pipermail/announce/2016-October/000061.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.