Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
sh: semanage: command not found #85
Chef client 14.2 changed the way execute works, from the release notes:
default_env Property in Execute Resource
The shell_out helper has been extended with a new option default_env to allow disabling Chef from modifying PATH and LOCALE environmental variables as it shells out. This new option defaults to true (modify the environment), preserving the previous behavior of the helper.
The execute resource has also been updated with a new property default_env that allows utilizing this the ENV sanity functionality in shell_out. The new property defaults to false, but it can be set to true in order to ensure a sane PATH and LOCALE when shelling out. If you find that binaries cannot be found when using the execute resource, default_env set to true may resolve those issues.
Steps to Reproduce:
Use chef-client 14.2, run from cron (we use sudo seems to inherit env and run just fine that way).
Chef client to run cleanly
I am seeing a similar issue with
This is happening on a RHEL 7.5 box, only during chef-client cron job run.
The problem is due to
If I modify the chef_client
What is the issue with CI?