Bug 1599275

Summary: Default ACL cannot be removed
Product: [Community] GlusterFS Reporter: homma
Component: posix-aclAssignee: bugs <bugs>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: mainlineCC: atumball, bugs
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-6.x Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1640109 (view as bug list) Environment:
Last Closed: 2019-06-18 10:02: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:

Description homma 2018-07-09 11:49:16 UTC
Description of problem:
Default ACL cannot be removed.

Version-Release number of selected component (if applicable):
glusterfs 3.12.6-1.el7 from centos-gluster312 repository

How reproducible:
Always

Steps to Reproduce:

1. Create a new directory and set default ACL.

$ mkdir test
$ setfacl -m d:g::rwx test
$ getfacl test
# file: test
# owner: root
# group: root
user::rwx
group::r-x
other::r-x
default:user::rwx
default:group::rwx
default:other::r-x

2. Remove the default ACL. The command completes with no error, but default ACL is not removed.

$ setfacl -k test

Actual results:

$ getfacl test
# file: test
# owner: root
# group: root
user::rwx
group::r-x
other::r-x
default:user::rwx
default:group::rwx
default:other::r-x

Expected results:

$ getfacl test
# file: test
# owner: root
# group: root
user::rwx
group::r-x
other::r-x

Additional info:

I have a replicated volume with 2 nodes, and the operation was done from a fuse client.

Volume Name: www
Type: Replicate
Volume ID: 797ded04-3a3b-497a-a16b-15a75f7e1550
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: fs21.localdomain:/glusterfs/www/brick1/brick
Brick2: fs22.localdomain:/glusterfs/www/brick1/brick
Options Reconfigured:
changelog.changelog: on
geo-replication.indexing: on
performance.client-io-threads: off
network.ping-timeout: 10
server.manage-gids: on
storage.build-pgfid: on
transport.address-family: inet
nfs.disable: on

Comment 1 homma 2018-10-18 11:32:21 UTC
I updated to version 4.1.5, but the problem is not resolved.
I have created a new case for version 4.1.5.

Comment 2 Shyamsundar 2018-10-23 14:54:45 UTC
Release 3.12 has been EOLd and this bug was still found to be in the NEW state, hence moving the version to mainline, to triage the same and take appropriate actions.

Comment 3 Amar Tumballi 2019-06-18 10:02:51 UTC
https://review.gluster.org/#/c/glusterfs/+/21411/ fixes the issue.