Bug 1643167

Summary: CephFS is creating exportable directories with 755 permission and causes containers not able to write on them using Manila
Product: Red Hat OpenStack Reporter: Alberto Gonzalez <alberto.gonzalez>
Component: openstack-manilaAssignee: Tom Barron <tbarron>
Status: CLOSED ERRATA QA Contact: Jason Grosso <jgrosso>
Severity: medium Docs Contact: mmurray
Priority: medium    
Version: 13.0 (Queens)CC: jdurgin, johfulto, lhh, nlevine, pdonnell, pgrist, racedoro, tbarron
Target Milestone: z5Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: openstack-manila-6.0.2-5.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1679273 (view as bug list) Environment:
Last Closed: 2019-03-14 13:34:19 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:
Bug Depends On: 1644421    
Bug Blocks: 1571739, 1679273    

Description Alberto Gonzalez 2018-10-25 16:01:09 UTC
Description of problem:

Using manila-provisioner in OpenShift creates a manila share on OpenStack. When is mounted on the POD:   2097152       0   2097152   0% /test-manila

The permissions are the following

sh-4.2$ ls -ld /test-manila/
drwxr-xr-x. 1 nobody nobody 0 Oct 25 15:34 /test-manila/

The user executing the pod is the following:
sh-4.2$ id
uid=1000180000 gid=0(root) groups=0(root),1000180000

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a PVC on Openshift
2. Wait till PV is created
3. Add volume for the pod in the deployment config 

Actual results:
Pod is not able to write in the NFS share due to 755

Expected results:
Able to write in the share, a 775 or 2775

Additional info:
Another option it would be create the directory with nfsnobody and run the containers following OCP instructions for NFS: 

Comment 6 errata-xmlrpc 2019-03-14 13:34:19 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.