I have been hesitant to file this bug because I do not have a clear understanding of why this is happening and if this is an intended behavior. Create a file called "C:\Program Files\Sysinternals\Config.bgi"
Have chef execute the following recipe:
This command should overwrite the acl on the file with a inherited acl (a work around for anther open bug). Note that the command fails with a return code of 42. When this command is run via command line the return code is always 0. Note that the command actually does what it is supposed to do (reset the dacl on the file), chef just erroneously reports return code 42.
This is not the only process that does this, I have another 5 or so examples which seemingly randomly return error code 42. Now a decent work around is to add 42 as a successful return code. We are doing this today, but is seems odd that I should have to deal with a seemingly "fake" return code.