Issue #21806 has been updated by Charlie Sharpsteen.

Description updated

----------------------------------------
Bug #21806: Puppetmaster 3.2.3-1puppetlabs1 not working with non-ascii 
characters
https://projects.puppetlabs.com/issues/21806#change-95877

* Author: Anton Markelov
* Status: Investigating
* Priority: Normal
* Assignee: Charlie Sharpsteen
* Category: utf8
* Target version: 
* Affected Puppet version: 3.2.3
* Keywords: utf8, encoding
* Branch: 
----------------------------------------
Hello all.

When I try to get configuration from server - it returns:

<pre>
"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 puppet.localnet
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run"
</pre>


My manifests contains comments on Russian (bad practice, I know, but my 
co-workers don't speak english). With puppetmaster 3.2.2-1puppetlabs1 (and 
below) all works correctly. 

<pre>
OS: Debian 7
Locale variables:
LANG=ru_RU.UTF-8
LANGUAGE=
LC_CTYPE="ru_RU.UTF-8"
LC_NUMERIC="ru_RU.UTF-8"
LC_TIME="ru_RU.UTF-8"
LC_COLLATE="ru_RU.UTF-8"
LC_MONETARY="ru_RU.UTF-8"
LC_MESSAGES="ru_RU.UTF-8"
LC_PAPER="ru_RU.UTF-8"
LC_NAME="ru_RU.UTF-8"
LC_ADDRESS="ru_RU.UTF-8"
LC_TELEPHONE="ru_RU.UTF-8"
LC_MEASUREMENT="ru_RU.UTF-8"
LC_IDENTIFICATION="ru_RU.UTF-8"
LC_ALL=ru_RU.UTF-8
</pre>


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to