[chef] RE: Re: chef-client first-run restorecon error

["Rechler, Mark" < >]

Thanks for the help Daniel! selinuxenabled was returning 0. Turned out to be this bug:
http://serverfault.com/questions/340679/centos-6-kickstart-ignoring-selinux-disabled

Setting a kernel option for selinux=0 made everything run correctly.

Thanks again,
Mark

---

From: Daniel DeLeo on behalf of Daniel DeLeo
Sent: Wednesday, November 06, 2013 10:27 AM
To:
Subject: [chef] Re: chef-client first-run restorecon error

On Wednesday, November 6, 2013 at 7:21 AM, Rechler, Mark wrote:

Hi All,

With the newer version of Chef, we're experiencing an odd error where the first run of chef-client (which is done during kickstart) dies when trying to render out the resolv.conf template:

Error executing action `create` on resource 'template[/etc/resolv.conf]

Mixlib::ShellOut::ShellCommandFailed^[[0m

------------------------------------^[[0m

Expected process to exit with [0], but received '1'

---- Begin output of /sbin/restorecon -R /etc/resolv.conf ----

STDOUT:

STDERR: No such file or directory

---- End output of /sbin/restorecon -R /etc/resolv.conf ----

Ran /sbin/restorecon -R /etc/resolv.conf returned 1^[[0m

The odd thing is selinux is disabled so it should not even be attempting a restorecon. The escape characters are somewhat concerning too.

Thanks in advance!

Mark

Chef runs `selinuxenabled` and checks the return code to determine if selinux is enabled. Do you know of a reason why this command could return 0 if selinux is actually disabled?

Code: https://github.com/opscode/chef/blob/master/lib/chef/util/selinux.rb

-- 

Daniel DeLeo