-
-
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
When defining a custom service & attaching to a zone - puppet errors and requires 2 runs #27
Comments
@dlevene1 wouldn't you need to restart firewall-cmd again after you add them to the zones? |
Yep, but when you add a service it's not "seen" until you restart. So when
|
@dlevene1 I think this is fixed with #30 - can you confirm? |
@jovandeginste I combined #30 and #31 in my tests and it all works as expected. I did noticed that on a custom zone the source's don't get applied until the second puppet run. See example below. So apart from the 2 puppet runs, it all looks good.
|
@dlevene1 #71 should solve this issue for you |
Thanks Craig! I might wait until the discussion on issue/26 is complete On 13 August 2016 at 18:12, Craig Dunn notifications@github.com wrote:
|
Released in 3.1.0 |
This is an ordering issue - but i'm not sure how to fix it.
We need to ensure that the custom_services are all defined and a reload of the firewall-cmd is done - then you can proceed to add them to the defined zones.
The text was updated successfully, but these errors were encountered: