Bug 1083816

Summary: DHT: Inconsistent permission on root directory of mount point after adding a new brick
Product: [Community] GlusterFS Reporter: Susant Kumar Palai <spalai>
Component: distributeAssignee: bugs <bugs>
Status: CLOSED EOL QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: pre-releaseCC: bugs, gluster-bugs, rgowdapp, social, srangana
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-22 15:40:20 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 Susant Kumar Palai 2014-04-03 03:33:53 UTC 
Description of problem:
DHT: Incosistent permission seen on root directory on mount point after adding a brick if the permission on the root has changed before adding the brick.

How reproducible:
Always

Steps to Reproduce:
1. Created a single brick volume 
[root@admin susant]# gvi
 
Volume Name: test1
Type: Distribute
Volume ID: 59b997a4-db0e-4d7b-9e2e-e2946cd99249
Status: Started
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: 192.168.122.1:/home/brick1/1
[root@admin susant]# 

2. Did fuse mount 
[root@admin susant]# glusterfs -s 192.168.122.1 --volfile-id test1 /mnt/dht/

[root@admin susant]# df -h | grep test1
192.168.122.1:test1             237G  203G   22G  91% /mnt/dht

3. Changed permission of root directory on mount point 
[root@admin dht]# pwd
/mnt/dht
[root@admin dht]# chown 777 .
[root@admin dht]# ll ..
total 20
drwxrwxrwx 3 root root 4096 Apr  3 08:51 dht <------ Note permission


4. Add a brick 

[root@admin susant]# gluster v add-brick test1 192.168.122.1:/home/brick1/2
volume add-brick: success
[root@admin susant]# gvi
 
Volume Name: test1
Type: Distribute
Volume ID: 59b997a4-db0e-4d7b-9e2e-e2946cd99249
Status: Started
Number of Bricks: 2
Transport-type: tcp
Bricks:
Brick1: 192.168.122.1:/home/brick1/1
Brick2: 192.168.122.1:/home/brick1/2
[root@admin susant]# 


5. Now check permission of root directory

[root@admin dht]# ll ..
total 20
drwxrwxrwx 3 root root 4096 Apr  3 08:51 dht <------Note permission (777)

[root@admin dht]# ll ..
total 20
drwxrwxrwx 3 root root 4096 Apr  3 08:51 dht <------Note permission (777)

[root@admin dht]# ll ..
total 28
drwxr-xr-x 3 root root 12288 Apr  3 08:55 dht <------ permission changed(755)

[root@admin dht]# ll ..
total 28
drwxr-xr-x 3 root root 12288 Apr  3 08:55 dht <------ permission changed(755)

[root@admin dht]# ll ..
total 28
drwxrwxrwx 3 root root 12288 Apr  3 08:55 dht <------ Permission changed to 777 again

[root@admin dht]# ll ..
total 28
drwxr-xr-x 3 root root 12288 Apr  3 08:55 dht <------- Now it is 755



Actual results:
After add brick, the mount point permission changes if the permission has changed before adding the brick.

Expected results:
Permission should be consistent.

Additional info:
Comment 1 Lukas Bezdicka 2014-04-03 06:27:25 UTC 
Probably duplicate of: https://bugzilla.redhat.com/show_bug.cgi?id=1063832
Comment 2 Kaleb KEITHLEY 2015-10-22 15:40:20 UTC 
pre-release version is ambiguous and about to be removed as a choice.

If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.