Because the serialization format (JSON) and the database both require UTF-8 character encoding for their data, puppetdb needs to encode strings before it sends them from the puppet master to the puppetdb server. Due to limitations in Puppet's representation of strings (character encoding is not explicitly specified), it's not possible for us to do anything too fancy when we encounter a byte sequence that is not directly representable in UTF-8. Thus, when this scenario occurs, you will see the warning that you mentioned. This does mean that we will be discarding the invalid bytes.
Whether or not this is cause for concern in your particular case depends on which resource triggered the warning, and what your use case for that resource is. If the offending resource is an exported resource that other nodes are relying on, then this could cause problems. If the offending resource is one that you query or report on, then your data could be skewed slightly. Otherwise, this is effectively harmless for you. One thing that we should do on our end, though, is try to provide a bit more context to the warning message to help you try to identify which resource is causing the warning. To that end I've filed the following ticket: http://projects.puppetlabs.com/issues/15016 (Also worth noting: in the existing/old storeconfigs, the behavior for handling this scenario is undefined... so for us, this warning is a first step towards providing comprehensive, robust support for handling string encoding.) We are definitely interested in hearing more details about your setup if this does cause you any problems. Thanks for the feedback! Chris On Wednesday, June 13, 2012 6:06:38 AM UTC-7, jcbollinger wrote: > > > > On Wednesday, June 13, 2012 5:51:22 AM UTC-5, A_SAAS wrote: >> >> Me again regarding puppetdb, I have the following warning message: >> "Jun 13 12:49:15 puppetmaster puppet-master[28444]: Ignoring invalid >> UTF-8 byte sequences in data to be sent to PuppetDB" >> >> Do I have to worry? >> > > I don't know any relevant specifics about PuppetDB, but on general > principles I would say that to the extent you rely on the data curated by > PuppetDB to be correct, yes, you should worry. The message suggests data > stream corruption between PuppetDB and whatever other part of the master is > talking to it at that point. Probably they disagree about what character > encoding to use, but whatever the cause of the problem, the message > suggests that PuppetDB interpreted the data in question differently than > its source intended. There is a bug of some kind in there, so I would file > a ticket. > > > John > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/PZtYDMbV1XQJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
