-
Notifications
You must be signed in to change notification settings - Fork 457
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
Persistence: may fail on fresh Debian nodes #134
Comments
Autorequire. It will silently fail if the class isn't there anyway. Just return a message about installing the firewall class or something if you think that is the reason for failing ... probably need a small mention of the firewall class in docs. |
dcarley
added a commit
to dcarley/puppetlabs-firewall
that referenced
this issue
Mar 1, 2013
autorequires from firewall and firewallchain resources to iptables and iptables-persistent packages, when the appropriate provider is selected and the packages are managed in the catalog. This will prevent failed rule creation and persistence on fresh nodes where the packages may not be pre-installed.
dcarley
added a commit
that referenced
this issue
Mar 1, 2013
kbarber
added a commit
that referenced
this issue
Mar 1, 2013
(GH-134) Autorequire iptables related packages
Fixed in #136 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Improvements on #133
Persistence may fail on fresh Debian/Ubuntu nodes if
Package['iptables-persistent']
isn't installed before the firstFirewall[]
resource is created.Possible solutions:
The text was updated successfully, but these errors were encountered: