-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatible encodings with ChefDK 0.10.0 and Windows 10 DE #332
Comments
sometimes the stack traces from cklient runs are less than helpful. Can you include the stack trace emitted when running with debug logging (`-l debug) or the one in the stacktrace.out file on the node? |
I found the problem: The user name contains non-ASCII characters (in this case a ü), so the path cannot be mapped. The stackrace (which unfortunately doesn't even hint at the problem):
|
The recipe referenced in the stacktrace is part of the windev cookbook and is nothing special (just iterating over an array and calling windows_package) |
I've been trying to repro this without luck but this is clearly an issue and doing some googling it appears to be a thing with ruby/windows. I am closing this and opening an issue in chef/mixlib-shellout#117 which is where the root of the problem lies. |
I'm having big trouble convincing Chef client to execute a recipe on a German Windows 10 installation.
The recipe is
and Chef ends with an incompatible encoding error (CP850 to ASCII-8BIT) and a message that points to the line beginning with nasty_tasks. But the error message mentions "block in from_file" and references the local cache which leads me to believe that someone forgot to read the files in with "rb". So this might be a core Chef error and not relevant to the cookbook...
Tried it with both ChefDK 0.9 and ChefDK 0.10. The system language (meaning the language Windows is installed in) needs to be other than English for this to be reproducible.
Same thing when using the windows_package resource.
windows cookbook version 1.38.2
Any hints on how to work around this other than reinstalling Windows?
The text was updated successfully, but these errors were encountered: