Bug 1554670
Summary: | [3.9] subpath volume mounts do not work with secret, configmap, projected, or downwardAPI volumes | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jordan Liggitt <jliggitt> | |
Component: | Storage | Assignee: | Jan Safranek <jsafrane> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jianwei Hou <jhou> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 3.9.0 | CC: | aos-bugs, aos-storage-staff, bchilds, dma, jsafrane, mifiedle, rbost, schoudha, tatanaka, xtian | |
Target Milestone: | --- | |||
Target Release: | 3.9.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Cause:
OpenShift did not check correctly for parent directories when creating SubPath.
Consequence:
Secrets, ConfigMap, DownwardAPI and Projected volumes could not be used with SubPaths in pods.
Fix:
OpenShift correctly evaluates parent directories.
Result:
Secrets, ConfigMap, DownwardAPI and Projected volumes can be used with SubPaths in pods.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1554864 1554865 1554866 1554868 1554869 1554871 1663260 (view as bug list) | Environment: | ||
Last Closed: | 2018-05-16 09:46:26 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: | 1554864, 1554865, 1554866, 1554868, 1554869, 1554871, 1663260 |
Description
Jordan Liggitt
2018-03-13 06:45:28 UTC
this affects use of subPath volume mounts with any secret, configmap, projected, or downwardAPI volume upstream fix in https://github.com/kubernetes/kubernetes/pull/61080 Origin 3.9 PR: https://github.com/openshift/origin/pull/18957 Verified this in openshift v3.9.7+d86a856. Subpath mounts work with secret, configmap, projected, or downwardAPI volumes. This bug slipped through cracks and has been fixed for a long time, at least since v3.9.16. |