Issue #12557 has been updated by zach armstrong.
Hi Chris,
I tested using the same format you tried (plus line numbers):
61: node testnode {
62: test::tester { "hello" }
63: }
64: define test::tester {
65: }
which resulted in
Feb 14 17:03:45 client1 puppet-agent[13108]: Starting Puppet client version
2.7.10
Feb 14 17:03:48 client1 puppet-agent[13108]: Could not retrieve catalog
from remote server: Error 400 on SERVER: Could not parse for environment
production: Syntax error at '}'; expected '}' at
/etc/puppet/manifests/site.pp:62 on node client1
Feb 14 17:03:48 client1 puppet-agent[13108]: Using cached catalog
Just in case this matters I am on Red Hat Enterprise Linux Server release 5.7
(Tikanga):
ruby-1.8.5-22.el5_7.1
ruby-libs-1.8.5-22.el5_7.1
ruby-augeas-0.4.1-1.el5
ruby-shadow-1.4.1-7.el5
libselinux-ruby-1.33.4-5.7.el5
And one other note, also updated to 2.7.10 (as seen in above log, no change.)
Let me know if there's anything else I could do to help.
----------------------------------------
Bug #12557: Inaccurate error message when calling a defined function without
colon after $name
https://projects.puppetlabs.com/issues/12557#change-54696
Author: zach armstrong
Status: Needs More Information
Priority: Low
Assignee: Chris Price
Category: error reporting
Target version:
Affected Puppet version: 2.7.9
Keywords:
Branch:
Calling a function, like
<pre>deploy::php_dev { "02" } </pre>
throws this error: `err: Could not retrieve catalog from remote server: Error
400 on SERVER: Could not parse for environment production: Syntax error at '}';
expected '}' at /etc/puppet/manifests/site.pp:72`
It should say `expected ':'`
--
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.
