On Fri, Jul 3, 2009 at 12:05 PM, Martin Wheldon<mwhel...@googlemail.com> wrote: > > Hi Curt, > > Did you manage to resolve this issue? If not I think it may be the > format of your yaml output. > >>--- >>classes: >>- custom >>- monitoring::base > > Should be this > > --- > classes: > - custom > - monitoring::base > > Note the indentation. Having said that I have been unable to persuade > the python yaml module to produce this > as yet. > > Hope this helps
Hey Martin, Thanks for the response. I did indeed get this working, it turns out it wasn't Puppet at all. The path for finding Python was incorrect, so while I was pointing it at /usr/local/bin/python it wasn't finding it and using /usr/bin/python which for some reason this script can't use (version issues). How and why this is, I don't know, but that's about as close to the reason as I was able to get. I think YAML is white space agnostic due to the '-' and ':' syntax. I could be wrong though. I hope to get some time and send in a patch to update the output on errors for executing external nodes, 4 days trying to figure out this issue was quite annoying and the error did little to help remedy the issue. Thanks again for the reponse, -- # Curt Micol --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
