Bug 1575503 - Cannot edit File mounted via configMap with subPath even after appending defaultMode: 0511
Summary: Cannot edit File mounted via configMap with subPath even after appending defa...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 3.7.0
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Bradley Childs
QA Contact: Jianwei Hou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-07 06:51 UTC by Madhusudan Upadhyay
Modified: 2018-05-07 17:40 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-07 17:40:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Madhusudan Upadhyay 2018-05-07 06:51:32 UTC
Description of problem:

Even after putting defaultMode: 0511 , editing file mounted via configMap with subPath, permission is denied stating: 'file is read-only'


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

3.7.44

How reproducible:

Always

Steps to Reproduce:
1. Set defaultMode: 0511 (which is translated to 777 on the pod)
2. Mount the file via configMap with Subpath
3. Edit the file(mounted via configMap). 

Actual results:
Cannot edit the file as file is readOnly

Expected results:
Successful edit of the file


Additional info:

Comment 1 Madhusudan Upadhyay 2018-05-07 06:54:23 UTC
Adding a reference Bugzilla for the issue:

https://bugzilla.redhat.com/show_bug.cgi?id=1481617

Comment 2 Madhusudan Upadhyay 2018-05-07 06:54:24 UTC
Adding a reference Bugzilla for the issue:

https://bugzilla.redhat.com/show_bug.cgi?id=1481617

Comment 3 Jordan Liggitt 2018-05-07 17:40:09 UTC
all atomic writer volumes (configmap, secret, projected, and downwardAPI) are always readonly, regardless of default mode or readOnly setting in the API.

see https://github.com/kubernetes/kubernetes/pull/58720


Note You need to log in before you can comment on or make changes to this bug.