Description of problem: Trace upstream issue in bugzilla for ocp-3.4 Upstream issue: https://github.com/kubernetes/kubernetes/issues/35406 Version-Release number of selected component (if applicable): openshift v3.4.0.18+ada983f kubernetes v1.4.0+776c994 etcd 3.1.0-rc.0 How reproducible: Alwyas Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This will be fixed by https://github.com/kubernetes/kubernetes/pull/35727
If emptydir is memory backed this will handle it https://github.com/kubernetes/kubernetes/pull/36779 PR in flight upstream to remove all volume for pods in a terminated state https://github.com/kubernetes/kubernetes/pull/37228
Upstream PR has merged https://github.com/kubernetes/kubernetes/pull/37228 Origin PR https://github.com/openshift/origin/pull/12669
This has been merged into ocp and is in OCP v3.5.0.12 or newer.
Verified on openshift v3.5.0.14+20b49d0 When pod is terminated, kubelet should remove disk backed emptydir volume. Steps: 1. Create Failed/Succeeded pods with host disk backed emptyDir volume $ oc create -f https://raw.githubusercontent.com/mdshuai/testfile-openshift/master/k8s/terminatedpods/emtydir-host.yaml 2. On node, Make sure disk backed emptyDir volume removed when pod become Failed/Succeeded # ls /var/lib/origin/openshift.local.volumes/pods/${pod.uid}/volumes/kubernetes.io~empty-dir/${volumeName}
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:0884