Bug 1318080 - Needs a way to avoid to set 777/nfsnobody permission to the NFS mount on persistent volume
Summary: Needs a way to avoid to set 777/nfsnobody permission to the NFS mount on pers...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Erin Boyd
QA Contact: Jianwei Hou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-16 01:16 UTC by Kenjiro Nakayama
Modified: 2019-10-10 11:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2016-03-17 22:03:38 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2200341 0 None None None 2016-03-16 01:34:16 UTC

Description Kenjiro Nakayama 2016-03-16 01:16:57 UTC 
Description of problem:

To use NFS as persisent volume on OSE v3, the user needs set the directory permission as 777/nfsnobody.
Otherwise, they need to set UID/GID on each docker images.

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

- 3.1.1.6

Additional info:

(RH internal discussion) http://post-office.corp.redhat.com/archives/openshift-sme/2016-February/msg01051.html
(upstream patch) https://github.com/kubernetes/kubernetes/pull/20490
Comment 1 Erin Boyd 2016-03-17 15:42:06 UTC 
This has already been addressed in the documentation for 3.1 and higher:
https://docs.openshift.com/enterprise/3.1/install_config/persistent_storage/persistent_storage_nfs.html

Please ensure you are following this guide for setup.
Note You need to log in before you can comment on or make changes to this bug.