-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
Firewalld not reloading in 3.0 #38
Comments
After manually doing a firewalld restart (yes, I even did the full restart)... I see the entries via iptables -L -n, but still can't connect. I'm comparing with our reference (non-puppeted) box and iptables -L -n matches exactly and zones/public.xml look the same.... sigh... but the reference box firewall allows the connection, and our puppeted box does not (sigh). We'll keep looking. But still, didn't seem to do the reload on its own, we forced it. |
What I have noticed is that the reload isnt enough. I created a service with this puppet module and the config shows up in /etc/firewalld/service/"name of service".xml . At that point I can do a reload or restart and the config still wont take affect. I have to run a firewall-cmd --permanent --add-service="name of service" in order for the config to actually go into effect. |
Are you using the latest version of the module? I'm using RHEL7 and I don't have any issues. The code here shows that it's doing a --permanent and a reload afterwards, so you should not have issues. |
In testing the latest version 3.0.1 I have been running into this issue with rich rules as well.
Once I issue
|
@BrandonIngalls are you sure you are including the firewall class ( |
We do have a problem here, we used to do collector syntax chaining to notify the exec to reload firewalld but now that notify is only valid for resources declared from the class (eg from hiera). The short term solution is to make sure you notify |
An easier (and more backwards compatible) fix will be just to reintroduce the chaining dependencies from init.pp that we dropped in 3.0.0, I can do that tomorrow as it's a minor bug fix |
Set dependencies using resource chaining so that resource declarations made outside of this class (eg: from the profile) also get their dependencies set automatically, this addresses various issues found in #38
@BrandonIngalls does #70 solve this issue for you? |
I've changed the topic of this issue to reflect the latest discussion, since the older posts were slightly different and fixed in 2.2 |
@crayfishx PR #70 does resolve this issue for me.
|
Released in 3.1.0 |
Is there anyway to force the firewall-cmd --reload
Here's what I have for a node:
firewalld_service { 'Allow postgresql':
ensure => 'present',
service => 'postgresql',
zone => 'public',
}
did I miss something easy in the docs? I thought I read that on any change a forced reload would get done, or something like that. I need at least a --reload done.
The text was updated successfully, but these errors were encountered: