-
Notifications
You must be signed in to change notification settings - Fork 62
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
Incompatibility with Puppet 4+ #31
Comments
This is still an issue with Puppet 4.x. I'm running Puppet 4.2.2
The line that is complaining about looks like:
|
@grantholly we're trying to resolve this by renaming and working around the limitations, if we can get it working I'll reach out and perhaps push it up. |
Ran into same problem. The solution is quite simple, yet tedious. You'll need to change all hardening manifests to be prefixed with a consistent string. For example, |
I can submit a pull request with the corresponding fix, if someone is will to review, and merge. |
I forgot I had posted this here, that's what we did, and then used a fancy for loop to edit all the files in one go and it's in use now. |
@AngelusDulcis, do you have your this module for puppet 4x available on a public repository? |
@jeff1evesque I do not, in the middle of the process for our own devices I excised many of the modules to fit our unique needs and it wouldn't be a "full" copy so I didn't make it available, sorry. |
I've made the class namespace changes, by adding a prefix Error: Failed to apply catalog: Parameter noop failed on Package[procps]: Invalid value "". Valid values are true, false. at /etc/puppetlabs/code/modules/sysctl/manifests/init.pp:145 Also, if I generalize this solution, for puppet 4x, do you guys want me to push commits to this repository? |
@jeff1evesque is that procps like - https://gitlab.com/procps-ng/procps -? |
@jeff1evesque I don't recall about others, but I did have procps-ng installed on the puppet server I am using it on. Maybe check and install it see if that resolves that issue? |
It seems this module is incompatible with the just released Puppet 4.
I haven't tested this yet on a VM myself, but the Travis CI builds that are used in testing Pull Requests fail big time. Example 1 and example 2:
After some Googling, this came up from the Puppetlabs website:
So for compatibility with Puppet 4.0.0+ it looks classes like el6::1_1_1 will need to be renamed to el6::c1_1_1 or something similar that makes seach namespace segment begin with a lowercase letter.
The text was updated successfully, but these errors were encountered: