[Pkg-puppet-devel] Bug#723188: puppetmaster: Non-ASCII characters in manifests break catalogs

[Roland Mas]

Package: puppetmaster
Version: 3.3.0-1
Severity: normal

My site.pp is encoded in UTF-8, and it contains non-ASCII characters
(French in comments).  Now the clients refuse to talk to it:

root at smiragdine:~# puppet agent --test
Info: Retrieving plugin
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not parse for environment production: invalid byte sequence in US-ASCII at /etc/puppet/manifests/site.pp:1 on node smiragdine.placard.fr.eu.org
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

I had seen this behaviour previously, and I had managed to work around
it by restarting puppetmaster while my locale was effectively
fr_FR.utf8.  It may be related to the recent upgrade to 3.3.0 that this
workaround no longer works; I can't pinpoint it directly, since I don't
run puppet as a daemon (I rather trigger the pulls with a custom
script).

Roland.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.10-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages puppetmaster depends on:
ii  init-system-helpers           1.8
ii  puppetmaster-common           3.3.0-1
ii  ruby                          1:1.9.3
ii  ruby1.8 [ruby-interpreter]    1.8.7.358-8
ii  ruby1.9.1 [ruby-interpreter]  1.9.3.448-1

puppetmaster recommends no packages.

puppetmaster suggests no packages.

-- Configuration Files:
/etc/default/puppetmaster changed:
START=yes
DAEMON_OPTS=""
export LANG=en_GB.UTF-8


-- no debconf information

-- 
Roland Mas

Two elephants fell off a cliff.
Boom, boom.