Issue #3799 has been updated by Alan Harder.
Really hope this will be looked at soon and can be fixed in the next release. We are prevented from upgrading to 0.25.5 to get other fixes due to this issue. Thanks. ---------------------------------------- Bug #3799: Reporting failed: "could not intern from yaml" if output ends in colon http://projects.puppetlabs.com/issues/3799 Author: Alan Harder Status: Investigating Priority: High Assigned to: Markus Roberts Category: serialization Target version: Affected version: 0.25.5 Keywords: Branch: One of our recipes we gets this with 0.25.5, ruby 1.8.7 on Solaris 10: <pre>err: Reporting failed: Error 400 on SERVER: Could not intern from yaml: syntax error on line 2819, col 61: ` message: You can find a log of this install session at:'</pre> The "message" listed above is part of the output from the recipe, from an exec resouce with logoutput => true. I can reproduce the problem with this simple test case: <pre>exec { 'echo foo:': logoutput => true }</pre> To workaround the warning message in the log about serialization format (which I understand in 0.25.5 final release is now "debug" level, yay), we had added this in puppet.conf: <pre>preferred_serialization_format = marshal</pre> I've now tried yaml, b64_zlib_yaml and pson instead but got the same error (specifying pson results in b64_zlib_yaml being used). raw got a different error. -- 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.
