Issue #4693 has been updated by micah -.
Tom Hod wrote: > it seems that the stage parameter can be globally unset by; > > stage => undef > > in site.pp Sure, but that is a 2.6 only parameter. If you set that and have any non-2.6 clients that run you will get: <pre> err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not parse for environment production: Syntax error at '=>' at /etc/puppet/manifests/site.pp:8 on node </pre> ---------------------------------------- Bug #4693: Invalid parameter stage error http://projects.puppetlabs.com/issues/4693 Author: micah - Status: Accepted Priority: Normal Assignee: Category: stages Target version: 2.6.1 Affected version: 2.6.1rc3 Keywords: Branch: Upgraded puppetmaster to 2.6-rc3 and ran a 0.25.5 puppet client against it and it compiled the manifest and then gave me this error: <pre>err: Could not run Puppet configuration client: Invalid parameter stage at /etc/puppet/manifests/common.pp:5</pre> I tried on another client and got a similar "Invalid parameter stage" error, but in a different part of the manifest. The common.pp line 5 is something I've had for a very long time: <pre> filebucket { main: server => 'puppetmaster.riseup.net'; } </pre> Upgrading the client to 2.6-rc3 made the error go away. -- 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.
