Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Chef falsely reports file not existing when it can't find the interpreter #8251
Chef was creating (from download) a file containing a python script, then attempting to execute it and reporting "No such file or directory" for the file it had just created. It turned out the problem was the script shebang line called
Correct behaviour would be what the shell does: Reporting
Create a file /tmp/foo.py with the first line having an invalid shebang path and have chef try to run it via an execute.
We don't parse anything inside of the script to change how we execute it and only call
This is accurately what
I'm not sure what the shell command line is doing to give back that exit status, but I'm more inclined to view this as correct behavior in the general case and not a bug.