Issue #22848 has been updated by Charles Olivier.

This issue seems to only affect the client side. 
Additionally, I found a quick fix, which works for me.
I use KVM on Debian 7.2 with Puppet 3 and The Foreman.
My VMs are a mix of Ubuntu and Debian boxes.  I use PXE and preseed to install 
guests.
I added the following to my /etc/default/puppet file in a post install script:

## export LANG=en_US.UTF-8

If you look in the puppet init.d script it sources the /etc/default/puppet file 
if it exists.
Thus the export is executed and the LANG environment variable is set.

I have tested with Ubuntu 13.10 and Debian 7.2 clients and i see no more red 
notifications in The Foreman.
I hope this helps anyone also frustrated with the lack of answers... :-)

----------------------------------------
Bug #22848: Encoding mis-matches cause package prefetching to fail
https://projects.puppetlabs.com/issues/22848#change-101384

* Author: Jos Backus
* Status: Investigating
* Priority: High
* Assignee: 
* Category: ruby19
* Target version: 
* Affected Puppet version: 3.3.1
* Keywords: utf8 encoding package customer
* Branch: 
----------------------------------------
One of our RPM packages has some UTF-8 characters in its description, leading 
to an exception ("Error: Could not prefetch package provider 'yum': invalid 
byte sequence in US-ASCII")  in rpm.rb, causing no packages to be upgraded as 
the yumhelper.py invocation code raises that error.

Priority=High because it breaks file { ensure => latest; }.


-- 
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