puppet does not correctly handle unusually encoded filenames in a file resource
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| puppet (Ubuntu) |
Confirmed
|
High
|
Unassigned | ||
Bug Description
Hi,
puppet fails to install file ressources from puppet:///... for some files with the error message
Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII
Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII
Wrapped exception:
invalid byte sequence in US-ASCII
Error: /Stage[
because it does not open files in :binary mode.
Just to have this bug known to ubuntu, I already have opened an upstream bug report more than a month ago, which unfortunately did not get any response yet:
https:/
regards
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: puppet (not installed)
ProcVersionSign
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelMo
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Apr 21 13:04:25 2014
SourcePackage: puppet
UpgradeStatus: No upgrade log present (probably fresh install)
| Hadmut Danisch (hadmut) wrote | #1 |
| Robie Basak (racb) wrote | #2 |
| Changed in puppet (Ubuntu): | |
| importance: | Undecided → High |
| Hadmut Danisch (hadmut) wrote | #3 |
| Launchpad Janitor (janitor) wrote | #4 |
| Changed in puppet (Ubuntu): | |
| status: | New → Confirmed |
| Robie Basak (racb) wrote Re: puppet does not correctly handle Unicode filenames in a file resource | #5 |
| summary: |
- Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII + puppet does not correctly handle Unicode filenames in a file resource |
| summary: |
- puppet does not correctly handle Unicode filenames in a file resource + puppet does not correctly handle unusually encoded filenames in a file + resource |
| Ben Hagen (c.ben.hagen) wrote | #6 |
Thank you for taking the time to report this bug and helping to make Ubuntu better.
I was unable to link the upstream bug to this one. Please can you comment here when there's some resolution on the debugging proceeding in the upstream bug?
It sounds to me that not being able to ensure a binary file exists is a significant regression, and if the fix is a simple patch then we can apply it to the stable release.