-
-
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 ignores custom zones at reboot but is ok after a manual restart #128
Comments
Are you including the firewalld base class? The module configures things in permenant mode so a restart is required to make changes active, though if you are including the firewalld base class these dependencies should already be set up for you |
I do yes - above the new firewalld zone config i've got: class { '::firewalld': } like this:
|
Can you paste the output of the puppet run when it first sets up the zone? It should restart the firewalld service for you |
It does do it's job on first run..........output below with lots of obfuscated internal ip addresses and names:
So far so good....puppet does it's job....but reboot the server and:
To be honest I'm emailing you but I'm veering towards it being more a problem for redhat. |
@rgill3003 Any update on this? It sounds like a strange Redhat issue but I don't want to close this ticket without a bit more info.... thx |
Just stumbled across this issue... I think this discussion may be helpful here. Although the firewalld man page states that firewalld tries to change the ZONE setting in the /etc/sysconfig/network-scripts/ifcfg- file, it does not appear to be doing so. It may be a bug in that program, but you may still be able to account for it in your module if you think it's a good idea. |
bizarre problem here - can't decide if it's one for redhat or whether it's to do with this puppet module.
IN our manifest we create a custom zone - one custom zone like so:
and then a few service and rich rules to go in there. Do a puppet run and everything works as expected. But reboot the server and everything doesn't work as expected - all traffic gets rejected...and sure enough:
.....but we haven't configured a public zone. OK - lets try a restart of firewalld:
weird huh? suddenly our custom zone called newzone becomes active and everything works as expected. Is this expected behaviour or am i doing something strange?
The text was updated successfully, but these errors were encountered: