-
-
Notifications
You must be signed in to change notification settings - Fork 881
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
Invalid parameter ensure at redhat.pp:49 #1065
Comments
What version of the module are you using? What version of puppet are you using? Have you tried without any parameters (no manage_repo or package_source)? |
I am using version 0.6.0 of the module puppet-nginx. I am using puppet version 3.4.3. I get the same error without any parameters. |
Oops! Just read the readme page again. Looks like I maybe need to upgrade puppet or downgrade the module version. |
BTW... Is there a way that I can specify the version of nginx to install? |
Downgraded to version 0.5.0 of the module puppet-nginx but still getting the same error: |
Are your dependencies OK? Have you tried running puppet in debug mode? |
I am running in debug mode. I don't see any dependency issues. It looks like this issue is with the following:
But not sure what that means exactly. Thanks so much for the assistance. It is greatly appreciated. I am pretty new to puppet and not loving it so far :-) Here is the log output:
|
I can't reproduce this. Please try to upgrade to 3.8.7 the last but now also unsupported release of the puppet 3.x series. The 0.6.0 module specifies only compatability with puppet Next version will only support puppet >= 4.6.x somewhat. Feel free to reopen if you can provide reproduction steps. |
I am getting an error:
Error: Invalid parameter ensure at /etc/puppet/modules/nginx/manifests/package/redhat.pp:49 on node mynode
My class definition looks like this:
class { 'nginx' :
manage_repo => true,
package_source => 'nginx-stable'
}
I am pretty new to Puppet and any assistance would be GREATLY appreciated!!
Thank you!
Ken
The text was updated successfully, but these errors were encountered: