>> YAML breaks when any of your parameter values end in a colon. I had >> tripped this once in the past but pson fixed this for me and so far I >> didn't have any further issues. Guess now a bug should be filed after all... > > Hmm, 0.24.x used YAML in its communication protocol, right? I have had > that particular resource in my manifests (applied on all nodes) for 23 > months, and I didn't switch to 0.25 until half a year later. Shouldn't > all my clients have failed to parse the catalog it received from the > master then?
Probably. Beatse me. But I remember running into issues during our 0.24 -> 0.25 upgrade. I enforced YAML serialization for a test, and many catalogs couldn't be transferred because of this issue. Those *did* work for 0.24 clients that may or may not have used YAML. So I'm somewhat stumped. The bug you found should probably addressed in any case. As a matter of fact, I have some parameters in my manifests that should trigger this, so I will try and reproduce one of these days... Cheers, Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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.
