Jira (PDB-2674) Problem with puppetdb encoding

[Angel L. Mateo (JIRA)]

Title: Message Title

Angel L. Mateo created an issue   PuppetDB / PDB-2674 Problem with puppetdb encoding Issue Type: Bug Affects Versions: PDB 2.3.8 Assignee: Unassigned Components: i18n Created: 2016/05/05 11:08 PM Priority: Normal Reporter: Angel L. Mateo I'm having a problem with puppetdb. I have deploy a new puppetserver (running in a ubuntu 14.04 server and installed from AIO package) that uses an already existing puppetdb (2.3.8, I know there are newer versions, but this puppetdb is also used by a puppet 3.8 master). With my current puppet 3.8 server I don't have any problem, but in the new puppetserver I'm having problem with the encoding of the stored resources. For example, I have a resource like this: @@omd_nagios_service {"${::nagios_hostname}_Trafico_eth0": ensure => hiera('profile::nagios::ensure', 'present'), host_name => $::nagios_hostname, service_description => 'Tráfico eth0', contact_groups => hiera('profile::nagios::contact_groups', undef), use => 'Servicio_Generico_Telematica_Grafica', check_command => 'check_interface_traffic!eth0 90 95 public 1000', tag => 'omd-nagios-telematica', site => 'telematica', } This resource is in catalogs applied in puppet 3.8 master and puppetserver. For clients using the puppet 3.8 master the information stored in the puppetdb database are like: resource | name | value ------------------------------------------+---------------------+-------------------------------------------------- 5aaad4db237176d84701792d35fd9c04ce0b26ae | check_command | "check_interface_traffic!eth0 90 95 public 1000" 5aaad4db237176d84701792d35fd9c04ce0b26ae | contact_groups | "" 5aaad4db237176d84701792d35fd9c04ce0b26ae | site | "telematica" 5aaad4db237176d84701792d35fd9c04ce0b26ae | use | "Servicio_Generico_Telematica_Grafica" 5aaad4db237176d84701792d35fd9c04ce0b26ae | host_name | "tlm_xenon21" 5aaad4db237176d84701792d35fd9c04ce0b26ae | ensure | "present" 5aaad4db237176d84701792d35fd9c04ce0b26ae | tag | "omd-nagios-telematica" 5aaad4db237176d84701792d35fd9c04ce0b26ae | service_description | "Tráfico eth0" but for clients in the new puppetserver are like: resource | name | value ------------------------------------------+---------------------+-------------------------------------------------- ff19d1eaf82d344bc406f6a4ba5b5c21d48fc10d | ensure | "present" ff19d1eaf82d344bc406f6a4ba5b5c21d48fc10d | host_name | "tlm_mus31" ff19d1eaf82d344bc406f6a4ba5b5c21d48fc10d | service_description | "Tr��fico eth0" ff19d1eaf82d344bc406f6a4ba5b5c21d48fc10d | use | "Servicio_Generico_Telematica_Grafica" ff19d1eaf82d344bc406f6a4ba5b5c21d48fc10d | check_command | "check_interface_traffic!eth0 90 95 public 1000" ff19d1eaf82d344bc406f6a4ba5b5c21d48fc10d | tag | "omd-nagios-telematica" ff19d1eaf82d344bc406f6a4ba5b5c21d48fc10d | site | "telematica" where the service_description attribute that should be Tráfico eth0 is Tr��fico eth0. I have checked that encoding in the database is correct: ~$ sudo -u postgres psql -P pager=off -l List of databases Name | Owner | Encoding | Collate | Ctype | Access privileges --------------+----------+----------+-------------+-------------+--------------------------- ... puppetdb | postgres | UTF8 | es_ES.UTF-8 | es_ES.UTF-8 | =T/postgres + | | | | | postgres=CTc/postgres + The only different I have found is that puppet 3.8 master (run with passenger) has LANG=C, but puppetserver java process has LANG=es_ES.UTF-8. Add Comment   This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.