From 7365a459d8e538815238bee1ad6dad6bf9954aa2 Mon Sep 17 00:00:00 2001 From: Eric Paris Date: Wed, 12 Nov 2014 16:52:38 -0500 Subject: [PATCH] do not fail build if unable to relabel selinux content If the failure is a problem, the build will fail later. But it is possible that this is not a fatal issue and we should let things go forward. (a filesystem mounted with context=something in permissive would cause chcon to fail, but the build to work) --- build/common.sh | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/build/common.sh b/build/common.sh index 06ca611c72a..b712560f989 100644 --- a/build/common.sh +++ b/build/common.sh @@ -190,9 +190,11 @@ function kube::build::prepare_output() { selinuxenabled && \ which chcon >/dev/null ; then if [[ ! $(ls -Zd "${LOCAL_OUTPUT_ROOT}") =~ svirt_sandbox_file_t ]] ; then - echo "+++ Applying SELinux policy to '_output' directory. If this fails it may be" - echo " because you have root owned files under _output. Delete those and continue" - chcon -Rt svirt_sandbox_file_t "${LOCAL_OUTPUT_ROOT}" + echo "+++ Applying SELinux policy to '_output' directory." + if ! chcon -Rt svirt_sandbox_file_t "${LOCAL_OUTPUT_ROOT}"; then + echo " ***Failed***. This may be because you have root owned files under _output." + echo " Continuing, but this build may fail later if SELinux prevents access." + fi fi fi