-
-
Notifications
You must be signed in to change notification settings - Fork 148
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
Problem with undef from left operand of 'in' at module.pp:38 #61
Comments
Also it seems some times my systems have this in their puppet reports, and selinux is completely disabled...
Which is a nasty side effect. |
I am facing the same problem. This module configures disables SELinux by default, setting SELINUX=disabled in /etc/selinux/config. Then after reboot SELinux will be disabled and puppet will fail with this error: "Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 'undef' from left operand of 'in' expression is not a string at /etc/puppet/modules/selinux/manifests/module.pp:38 on node" |
@salderma Spoke too soon. This module will still not run when SELinux is disabled. puppet agent stops with the same error as above. My guess is that this error is is because the module does not handle SELinux being disabled. |
@mikalsande you are correct. I guess I'm just going to break it down and hardcode the params.pp to enforcing like you suggested in another issue. |
It seems there was a bug related to this #64 |
The problem here seems to be the use of |
this should be addressd in the current version. if you still see this problem, please re-open the issue. |
Hi, I am using your module from puppetforge to deploy a simple selinux policy.te file to many nodes like so:
All agents where this is applied fail with:
I am not using any references or resources from your module anywhere else for these nodes manifests. I am not following why there needs to be a global param defined to set the selinux policy. Shouldn't this be a module param? Can you provide any advice?
Thanks!
The text was updated successfully, but these errors were encountered: