Issue #4703 has been reported by micah -.

----------------------------------------
Bug #4703: Could not intern from b64_zlib_yaml: allocator undefined for Proc
http://projects.puppetlabs.com/issues/4703

Author: micah -
Status: Unreviewed
Priority: Normal
Assignee: 
Category: reports
Target version: 
Affected version: 2.6.1rc3
Keywords: 
Branch: 


In 0.25.4 puppet would spit this into the logs:

<pre>
puppetd[2100]: Value of 'preferred_serialization_format' (pson) is invalid for 
report, using default (b65_zlib_yaml)
</pre>

I wanted that to stop, so I used the hint from #2837 to make it stop by placing 
this in my puppet.conf template:
<pre>
preferred_serialization_format=b64_zlib_yaml
</pre>

That worked great, until I upgraded to 2.6.1-rc3, and now the catalog cannot be 
compiled:

<pre>
info: Retrieving plugin
info: Loading facts in mysql
info: Loading facts in interfaces
info: Loading facts in acpi_available
info: Loading facts in public_ip
info: Loading facts in diskdrives
info: Loading facts in sshkeys
err: Could not retrieve catalog from remote server: Could not intern from 
b64_zlib_yaml: allocator undefined for Proc
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
</pre>

If I remove it from puppet.conf, then things work again. But this means I need 
to downgrade my puppetmaster just in order to fix this. I have to remove it 
from the template and let that be applied everywhere, and then I can upgrade 
back to 2.6.1. Until then, I can't fix this using 2.6.1


-- 
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 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-bugs?hl=en.

Reply via email to