Description of problem: Version-Release number of selected component (if applicable): 3.9.7-1 How reproducible: Always Steps to Reproduce: 1. Create a pod with a secret, configmap, downwardAPI and projected volume 2. Create volume mounts for each of those volumes that make use of the subPath feature Actual results: The pod will not start with errors like failed to prepare subPath for volumeMount "config" of container "mumble": subpath "/var/lib/kubelet/pods/66fa673c-266d-11e8-8ebf-00155d00a406/volumes/kubernetes.io~configmap/config/..2018_03_13_03_19_55.572152209/mumble.ini" not within volume path "/var/lib/kubelet/pods/66fa673c-266d-11e8-8ebf-00155d00a406/volumes/kubernetes.io~configmap/config" Expected results: Pod starts properly and volume mounts work Regression introduced as part of the fix for https://bugzilla.redhat.com/show_bug.cgi?id=1519365 Upstream issue: https://github.com/kubernetes/kubernetes/issues/61076#issuecomment-372554309 The security fix was backported all the way to 3.3, which means this regression was as well.
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.