Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1445523

Summary: [3.5] Subpath does not receive right permissions
Product: OpenShift Container Platform Reporter: Paul Morie <pmorie>
Component: StorageAssignee: Paul Morie <pmorie>
Status: CLOSED ERRATA QA Contact: Jianwei Hou <jhou>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.5.1CC: aos-bugs, eparis
Target Milestone: ---   
Target Release: 3.5.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1445526 (view as bug list) Environment:
Last Closed: 2017-06-15 18:38:04 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:
Bug Depends On:    
Bug Blocks: 1445526    

Description Paul Morie 2017-04-25 21:20:19 UTC 
Description of problem:

If a subpath is used to mount a volume, the subpath may not receive correct permissions.

See: https://github.com/kubernetes/kubernetes/issues/41638

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

3.5

How reproducible:

Mount a volume via a subpath in the volumemount and try to write to it as a non-root user.

Actual results:

Not writable

Expected results:

Writable

Additional info:


Description of problem:

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

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

Additional info:
Comment 1 Eric Paris 2017-04-25 21:23:28 UTC 
3.5 PR
https://github.com/openshift/ose/pull/725
Comment 2 Jianwei Hou 2017-04-27 06:59:42 UTC 
Verified subPath is writable 3.5.5.10-1.
Comment 4 Jianwei Hou 2017-06-05 06:41:30 UTC 
Verified on v3.5.5.23
Comment 6 errata-xmlrpc 2017-06-15 18:38:04 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.

https://access.redhat.com/errata/RHBA-2017:1425