-
Notifications
You must be signed in to change notification settings - Fork 456
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
Compatibility with Puppet 4 and Facter 3 #559
Conversation
+1 |
It would be appreciated if you could give me your puppet --version and facter --version as I can't actually reproduce this issue. Thanks |
@jonnytpuppet I have the issue with puppet-agent 1.2.1 |
I'm using puppet-agent-1.2.1-1.el7.x86_64 on EL7 and don't see this... Can you provide a manifest that brings up the error please? |
Facter Version 3.0.1 (commit 9b1ef723a1494a01e0eccfe93a75fd43316690c2) |
Puppet Agent 1.2.1 |
I'm using the same version and not seeing this. Can you please confirm if this only happens during the first run? Does it happen after you restart your puppet server? This could be a known bug in Puppet 4.2.0 that is not related to the firewall module. |
I'm closing this as the .fact method was never removed. You could be hitting another Puppet bug. |
This will manifest only when running under Puppet Server and not an MRI master. Because Facter 3 is entirely native code, we decided to only implement the minimum set of the Facter API to get it working under a JRuby environment, which is what Puppet Server is. Thus While |
Thanks @peterhuene I'll submit another PR as the unit tests need updated |
To be clear, this is what we're seing when using the Firewall module with Puppet 4:
|
Compatibility with Puppet 4 and Facter 3
Compatibility with Puppet 4 and Facter 3
No description provided.