Description of problem: Version-Release number of selected component (if applicable): firewalld-0.3.13-5.fc22 How reproducible: Every time Steps to Reproduce: 1. Install a Fedora 22 Branched or Rawhide Compose after May 11th Actual results: The installed system will get the default (non-product) firewall configuration, not the Edition-specific one. Expected results: The installed system should get the correct set of default firewall rules. Additional info: This does not affect upgraded systems, due to the nature of the bug. The issue is that we accidentally pushed the updated fedora-release package to stable before the firewalld package (which did not happen in time for Freeze). I forgot to build the matching firewalld package in time. The issue is fixed in firewalld-0.3.13-7.fc22
Proposed as a Blocker for 22-final by Fedora user sgallagh using the blocker tracking app because: "After system installation without explicit firewall configuration, the system firewall must be active on all non-loopback interfaces. The only ports which may be open to incoming traffic are port 22 (ssh), port 9090 (Cockpit web interface), and any ports associated with server Roles selected during installation. Supported install-time firewall configuration options must work correctly." (Alpha Criterion)
firewalld-0.3.13-7.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/firewalld-0.3.13-7.fc22
For the record, +1 blocker from me.
+1 Blocker.
+1 blocker, that's +3, moving to accepted.
Tested the fix by creating a Workstation live, it looks good.
firewalld-0.3.13-7.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.