On Fri, Nov 19, 2010 at 11:01 AM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:
> On 11/19/2010 10:56 AM, Chris May wrote:
> >
> > Thinking back to the original PSON bug, the workaround back then was
> > to use YAML serialization. I did notice that that could make clients
> > crash though, I think the 0.25.5 were the afflicted ones.
> >
> > You may want to give it shot though, anyway. The YAML encoder seems
> > to be less picky where encodings are concerned.
> >
> > Alas, that doesn't work for me either; I get
> >
> > err: Could not retrieve catalog from remote server: Could not intern
> > from yaml: can't convert Array into String
>
> I see, but this is plain stupid. Such things are not supposed to happen.
>
> You may want to find out which part of your catalogue causes this (i.e.,
> which subset of your manifest is sufficient to reproduce this behaviour)
> and raise a bug.
>
This is with 2.6.3 on both client and server; the relevant portion of the
catalog (sufficient to cause the error on its own) is
file{"/tmp/test": content=>"/var/puppet/private/truststore"}
/var/puppet/private/truststore is a JKS-encoded keystore.
I imagine (though I haven't actually debugged it) that the error is because
one element the array being serialized is is the contents of this file,
which includes the non-UTF-8 bytes which cause the serialization error in
PSON. If that's true, I would expect that a fix for
http://projects.puppetlabs.com/issues/5261 would probably fix the YAML issue
as well.
thanks
Chris
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
