I've narrowed the error down to puppet mishandling the parsing of my
function.
I am using the aws-sdk in my custom function and I can connect fine, but as
soon as I try to iterate or filter an EC2InstanceCollection, thats when I
get the "wrong header line format" error on the node.
E.g:
ec2 = AWS.ec2(:region=>"us-west-2") # works fine, connection established
ec2.instances.tagged("TAG").tagged_values("VALUE").each do | instance | ...
end # anything here fails, I've tried filter as well.
This is really strange, as when I run the function in a test manifest it
works correctly.
On Tuesday, May 14, 2013 8:14:17 PM UTC-4, David Pires wrote:
>
> I have a custom function (
> http://docs.puppetlabs.com/guides/custom_functions.html) working locally
> using `puppet apply --modulepath=` and a test manifest.
>
> The issue I am having is when I run it on a node I get a "wrong header
> line format" error on the puppet master and I can't figure out why. It is
> not a erb template issue as I have tested all my erb's and they are fine, I
> have pinpointed the error to wherever I use the function.
>
> I have run through all the troubleshooting steps (irb, ruby -rpuppet etc.)
> they all work correctly. The same error occurs whether I use the function
> in my main site manifest or through a module class.
>
> Any help to further debug this is appreciated.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
