Origin: oc cluster down leaves secret mount points in volume directory

Created on 27 Feb 2017 · 3Comments · Source: openshift/origin

After running oc cluster down secret mount points remain mounted in the --host-volumes-dir

Version

oc v1.5.0-alpha.1+71d3fa9
kubernetes v1.4.0+776c994
features: Basic-Auth GSSAPI Kerberos SPNEGO

Steps To Reproduce

oc cluster up --host-volumes-dir=/tmp/test-volumes
_do something_
oc cluster down
rm -rf /tmp/test-volumes

Current Result

Cannot clear out the volumes directory, e.g.
rm: cannot remove '/tmp/test-volumes/pods/61cadc36-fab1-11e6-abd2-507b9dcf147a/volumes/kubernetes.io~secret/router-token-imy4z': Device or resource busy

Expected Result

oc cluster down to return to umount'd state

Additional Information

Little workaround line to umount (but make sure the grep works for you!)
for m in $(mount | grep pods | awk '{print $3}'); do umount $m ; done

componencluster-up kinbug prioritP2

Source

edseymour

Most helpful comment

I'd recommend findmnt -r -n -o TARGET |grep /var/lib/origin | xargs -r umount as it's less string parsing. (In general, I always use findmnt nowadays to display mounts)

cgwalters on 28 Feb 2017

👍4 ❤1

All 3 comments

I'd recommend findmnt -r -n -o TARGET |grep /var/lib/origin | xargs -r umount as it's less string parsing. (In general, I always use findmnt nowadays to display mounts)

cgwalters on 28 Feb 2017

👍4 ❤1

Those mounts are eventually removed by the kubelet when you start the cluster again, but yes agree that they could be removed.