-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
params_lookup and puppet 3 #40
Comments
I'm not able to reproduce the error (https://travis-ci.org/example42/puppet-dhcpd) |
I have two environments. Both Solaris. First it works in this environment. The problematic setup is a clone of the master which has been upgraded. Modules: |
Have you been able to reproduce this? |
Sorry, no. I tested on a Puppet 3.1.1 (on Linux) without problems. The issue is potentially serious anyway, because params_lookup is at the core or Example42 modules, so this has to be investigaed. Can you try some changes on the first line of the resolver where params_lokup is used and see if the error "shitfs" to the following line:
try:
or
and let me know if:
becomes:
|
I will look into this next week. |
I can not reproduce this anymore either. Strange. |
Well, suppose (and hope) I can close the issue |
When using these modules on Puppet ver 3 I get these errors:
err: Could not retrieve catalog from remote server: Error 400 on SERVER: custom functions must be called with a single array that contains the arguments. For example, function_example([1]) instead of function_example(1) at /etc/puppet/modules/resolver/manifests/init.pp:148 on node puppetclient
The text was updated successfully, but these errors were encountered: