Bug 981652 - firewalld does not cover openstack/packstack use case.
Summary: firewalld does not cover openstack/packstack use case.
Alias: None
Product: Fedora
Classification: Fedora
Component: firewalld
Version: 20
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Thomas Woerner
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: 981583 1099840 1103315
TreeView+ depends on / blocked
Reported: 2013-07-05 12:10 UTC by Matthew Miller
Modified: 2015-06-29 12:03 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 981583
Last Closed: 2015-06-29 12:03:13 UTC
Type: Bug

Attachments (Terms of Use)

Description Matthew Miller 2013-07-05 12:10:56 UTC
Projects building on Fedora should not be forced to learn a special new language; need to make it easy for these projects to directly use their existing rules.

From bug #981583:

Description of problem:
Firewall rules are applied by packstack via iptables, but in f19 the default firewall management tool is firewalld, this means that the rules are not persistent across reboot if firewalld is enabled.

Version-Release number of selected component (if applicable):

How reproducible:
Always if firewalld is enabled and iptables is not.

Steps to Reproduce:
1. run packstack
2. reboot

Actual results:
After the reboot "iptables -L" shows no packstack specific rules.

Expected results:
There should be firewall rules for openstack present after reboot.

Additional info:
This can be fixed by disabling/stopping the firewalld service and enabling/starting the iptables service.

Comment 1 Fedora End Of Life 2013-09-16 14:24:07 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:

Comment 2 Adam Young 2014-01-09 04:42:11 UTC
The basic premise of this bug is wrong:  IP tables should not be blindly carried over to FirewallD.

What needs to happen is the OpenStack services need firewallD rules, like were done in https://bugzilla.redhat.com/show_bug.cgi?id=914859

Comment 3 Fedora End Of Life 2015-05-29 09:09:34 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-06-29 12:03:13 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.