Skip to content
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

comment property does not work #131

Open
linuxdan opened this issue Jul 31, 2014 · 7 comments
Open

comment property does not work #131

linuxdan opened this issue Jul 31, 2014 · 7 comments

Comments

@linuxdan
Copy link

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter comment on Sysctl[net.ipv6.conf.default.accept_redirects] at /etc/puppet/modules/System_config/manifests/init.pp:252 on node devserver.example.com

@raphink
Copy link
Member

raphink commented Aug 6, 2014

Can you show your Puppet code please?

@linuxdan
Copy link
Author

linuxdan commented Aug 6, 2014

Like this:

    sysctl { 'net.ipv6.conf.default.accept_redirects':
        ensure    => 'present',
        value     => '0',
        comment => "Disable ipv6 redirects",
    }

@raphink
Copy link
Member

raphink commented Nov 17, 2014

Are you using another sysctl module at the same time?

@raphink
Copy link
Member

raphink commented Nov 17, 2014

It seem #129 indicates you are using another module, which provides a different, incompatible type. You need to choose which one you want to use (or ask @fiddyspence if he would depend on augeasproviders_sysctl for his resource type instead.

@linuxdan
Copy link
Author

Suggestion: Collaborate with @fiddyspence and fix the problem

“Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” (Bill Waterson: Calvin & Hobbes)

On Nov 17, 2014, at 09:19 AM, Raphaël Pinson notifications@github.com wrote:

It seem #129 indicates you are using another module, which provides a different, incompatible type. You need to choose which one you want to use (or ask @fiddyspence if he would depend on augeasproviders_sysctl for his resource type instead.


Reply to this email directly or view it on GitHub.

@fiddyspence
Copy link

I kind of agree that it's just a conflict here. The types/modules are named the same thing, and I'm not hugely inclined to rename the type. I'm also not a huge augeas fan, so migrating to using augeasproviders isn't really on my radar - I don't want the type to have that kind of external library dependency hence the ruby file munging.

@raphink
Copy link
Member

raphink commented Dec 1, 2014

I was going to say we could share a common type, but then I had a closer look at @fiddyspence's module, and it really does just the same thing as this one, except without using Augeas.

So, @linuxdan, what could be the reason for wanting to use both at the same time?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants